View 28F128W30_2974463.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

order number: 290702-13 november 2007 numonyx? wireless flash memory (w30) 28f640w30, 28f320w30, 28F128W30 datasheet product features ? high performance read-while-write/erase ? burst frequency at 40 mhz ? 70 ns initial access speed ? 25 ns page-mode read speed ? 20 ns burst-mode read speed ? burst-mode and page-mode in all blocks and across all partition boundaries ? burst suspend feature ? enhanced factory programming: 3.5 s per word program time ? programmable wait signal polarity ? flash power ?v cc = 1.70 v ? 1.90 v ?v ccq = 2.20 v ? 3.30 v ? standby current (130 nm) = 8 a (typ.) ? read current = 7 ma (4 word burst, typical) ? flash software ? 5 s/9 s (typ.) program/erase suspend latency time ? numonyx? flash data integrator (fdi) and common flash interface (cfi) compatible ? quality and reliability ?operating temperature: ?40 c to +85 c ? 100k minimum erase cycles ? 130 nm etox? viii process ? 180 nm etox? vii process ? flash architecture ? multiple 4-mbit partitions ? dual operation: rww or rwe ? parameter block size = 4-kword ? main block size = 32-kword ? top or bottom parameter blocks ? flash security ? 128-bit protection register: 64 unique device identifier bits; 64 user otp protection register bits ? absolute write protection with v pp at ground ? program and erase lockout during power tra nsiti ons ? individual and instantaneous block locking/unlocking with lock-down ? density and packaging ? 130 nm: 32mb, 64mb, and 128mb in vf bga package; 64mb, 128mb in quad+ package ? 180 nm: 32mb and 128mb densities in vf bga package; 64mb density in bga* package ? 56 active ball matrix, 0.75 mm ball-pitch ? 16-bit data bus
datasheet november 2007 2 order number: 290702-13 legal lines and disc laim ers information in this document is provided in connection with numonyx? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. except as provided in numonyx's terms and conditions of sale for such products, numonyx assumes no liability whatsoever, and numonyx disclaims any express or implied warranty, relating to sale and/or use of numonyx products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear f acility applications. numonyx b.v. may make changes to specifications and product descriptions at any time, without notice. numonyx b.v. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights tha t relate to the presented subject matter. the furnishing of documents and other materials and information does not provide any license, express or implie d, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? num onyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. contact your local numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. copies of documents which have an order number and are referenced in this document, or other numonyx literature may be obtained by visiting numonyx's website at http://www.numonyx.com . numonyx, the numonyx logo, and strataflash are trademarks or registered trademarks of numonyx b.v. or its subsidiaries in other countries. *other names and brands may be claimed as the property of others. copyright ? 2007, numonyx b.v., all rights reserved.
november 2007 datasheet order number: 290702-13 3 numonyx? wireless flash memory (w30) contents 1.0 introduction .............................................................................................................. 7 1.1 document purpose .............................................................................................. 7 1.2 nomenclature ..................................................................................................... 7 1.3 conventions ....................................................................................................... 8 2.0 functional overview .................................................................................................. 9 2.1 overview ........................................................................................................... 9 2.2 memory map and partitioning .............................................................................. 10 3.0 package information ............................................................................................... 13 3.1 w30 flash memory device ? 130 nm lithography .................................................. 13 3.2 w30 flash memory device ? 180 nm lithography .................................................. 15 4.0 ballout and signal descriptions ............................................................................... 18 4.1 signal ballout ................................................................................................... 18 4.2 signal descriptions ............................................................................................ 20 5.0 maximum ratings and operating conditions ............................................................ 24 5.1 absolute maximum ratings................................................................................. 24 5.2 operating conditions ......................................................................................... 24 6.0 electrical specifications ........................................................................................... 26 6.1 dc current characteristics.................................................................................. 26 6.2 dc voltage characteristics.................................................................................. 27 7.0 ac characteristics ................................................................................................... 28 7.1 read operations - 130 nm lithography ................................................................ 28 7.2 read operations - 180 nm lithography ................................................................ 29 7.3 ac write characteristics ..................................................................................... 38 7.4 erase and program times................................................................................... 43 8.0 power and reset specifications ............................................................................... 44 8.1 active power..................................................................................................... 44 8.2 automatic power savings (aps) .......................................................................... 44 8.3 standby power.................................................................................................. 44 8.4 power-up/down characteristics........................................................................... 44 8.4.1 system reset and rst#.......................................................................... 45 8.4.2 vcc, vpp, and rst# transitions............................................................... 45 8.5 power supply decoupling ................................................................................... 45 8.6 reset specifications........................................................................................... 46 8.7 ac i/o test conditions....................................................................................... 46 8.8 flash device capacitance ................................................................................... 47 9.0 flash device operations .......................................................................................... 48 9.1 bus operations ................................................................................................. 48 9.1.1 read .................................................................................................... 48 9.1.2 burst suspend ....................................................................................... 49 9.1.3 standby ................................................................................................ 49 9.1.4 reset.................................................................................................... 50 9.1.5 write .................................................................................................... 50 9.2 flash device commands..................................................................................... 50 9.3 command sequencing ....................................................................................... 53 10.0 read operations ...................................................................................................... 55 10.1 read array ....................................................................................................... 55
numonyx? wireless flash memory (w30) datasheet november 2007 4 order number: 290702-13 10.2 read device id .................................................................................................55 10.3 read query (cfi) ..............................................................................................56 10.4 read status register..........................................................................................56 10.5 clear status register .........................................................................................58 11.0 program operations .................................................................................................59 11.1 word program ...................................................................................................59 11.2 factory programming .........................................................................................60 11.3 enhanced factory program (efp) .........................................................................61 11.3.1 efp requirements and considerations .......................................................61 11.3.2 setup....................................................................................................62 11.3.3 program ................................................................................................62 11.3.4 verify....................................................................................................62 11.3.5 exit.......................................................................................................63 12.0 program and erase operations .................................................................................65 12.1 program/erase suspend and resume ...................................................................65 12.2 block erase .......................................................................................................67 12.3 read-while-write and read-while-erase ...............................................................69 13.0 security modes ........................................................................................................71 13.1 block lock operations ........................................................................................71 13.1.1 lock......................................................................................................72 13.1.2 unlock...................................................................................................72 13.1.3 lock-down ............................................................................................72 13.1.4 block lock status ...................................................................................73 13.1.5 lock during erase suspend ......................................................................73 13.1.6 status register error checking .................................................................74 13.1.7 wp# lock-down control ..........................................................................74 13.2 protection register.............................................................................................75 13.2.1 reading the protection register ................................................................76 13.2.2 programing the protection register ...........................................................76 13.2.3 locking the protection register.................................................................76 13.3 vpp protection...................................................................................................78 14.0 set read configuration register ..............................................................................79 14.1 read mode (rcr[15]) ........................................................................................80 14.2 first access latency count (rcr[13:11]) ..............................................................80 14.2.1 latency count settings............................................................................81 14.3 wait signal polarity (rcr[10]) ...........................................................................81 14.4 wait signal function .........................................................................................82 14.5 data hold (rcr[9])............................................................................................82 14.6 wait delay (rcr[8]) .........................................................................................83 14.7 burst sequence (rcr[7])....................................................................................83 14.8 clock edge (rcr[6]) ..........................................................................................85 14.9 burst wrap (rcr[3]) ..........................................................................................85 14.10 burst length (rcr[2:0]).....................................................................................85 a write state machine .................................................................................................86 b common flash interface ..........................................................................................89 c ordering information ...............................................................................................99
november 2007 datasheet order number: 290702-13 5 numonyx? wireless flash memory (w30) revision history date of revision version description 09/19/00 -001 initial release 03/14/01 -002 28f3208w30 product references removed (product was discontinued) 28f640w30 product added revised table 2, signal descriptions ( dq 15?0 , adv#, wait, s-ub#, s-lb#, v ccq ) revised section 3.1, bus operations revised table 5, command bus definitions , notes 1 and 2 revised section 4.2.2, first latency count (lc 2?0 ); revised figure 6, data output with lc setting at code 3 ; added figure 7, first access latency configuration revised section 4.2.3, wait signal polarity (wt) added section 4.2.4, wait signal function revised section 4.2.5, data output configuration (doc) added figure 8, data output configuration with wait signal delay revised table 13, status register dws and pws description revised entire section 5.0, program and erase voltages revised entire section 5.3, enhanced factory programming (efp) revised entire section 8.0, flash security modes revised entire section 9.0, flash protection register ; added table 15, simultaneous operations allowed with the protection register revised section 10.1, power-up/down characteristics revised section 11.3, dc characteristics. c hanged i ccs, i ccws, i cces specs from 18 a to 21a; changed i ccr spec from 12 ma to 15 ma (burst length = 4) added figure 20, wait signal in synchronous non-read array operation waveform added figure 21, wait signal in asynchronous page-mode read operation waveform added figure 22, wait signal in asynchronous single-word read operation waveform revised figure 23, write waveform revised section 12.4, reset operations clarified section 13.2, sram write operation , note 2 revised section 14.0, ordering information minor text edits 04/05/02 -003 deleted sram section added 128m dc and ac specifications added burst suspend added read while write transition waveforms various text edits 04/24/02 -004 revised device id revised write speed bin various text edits 10/20/02 -005 added latency count tables updated packing ball-out and dimension various text edits minor text clarifications 01/14/03 -006 revised table 20, dc current characteristics, i ccs revised table 20, dc current characteristics, i ccaps removed numonyx burst order minor text edits updated package drawing and dimensions 03/22/03 -007 revised table 22, read operations, t apa added note to table 15, configuration register descriptions added note to section 3.1.1, read
numonyx? wireless flash memory (w30) datasheet november 2007 6 order number: 290702-13 11/17/03 -008 updated block lock operations (sect. 7.1 and fig. 11) updated improved ac timings added quad+ package option, and appendix d minor text edits including new product-naming conventions 05/06/04 -009 corrected absolute maximum rating for v ccq (sect. 10.1, table 18) minor text edits 05/17/04 -010 restructured the datasheet according to new layout. 06/2005 -011 timing diagram nomenclature synergy with other product families added ordering information minor text edits 08/2007 -012 updated ordering information november 2007 13 applied numonyx branding. date of revision version description
november 2007 datasheet order number: 290702-13 7 numonyx? wireless flash memory (w30) 1.0 introduction the numonyx? wireless flash memory (w30) device combines state-of-the-art numonyx? flash technology to provide a versatile memory solution for high performance, low power, board constraint memory applications. the w30 flash memory device offers a multi-partition, dual-operation flash architecture that enables the flash device to read from one partition while programming or erasing in another partition. this read-while-write or read-while-erase capability makes it possible to achieve higher data throughput rates compared to single partition devices. two processors can interleave code execution, because program and erase operations can now occur as background processes. the w30 flash memory device incorporates an enhanced factory programming (efp) mode to improve 12 v factory programming performance. this feature helps eliminate manufacturing bottlenecks associated with programming high-density flash memory devices. the efp program time is 3.5 s per word, compared to the standard factory program time of 8.0 s per word, so efp mode saves significant factory programming time for improved factory efficiency. t he w30 flash memory device also includes block lock-down and programmable wait signal polarity, and is supported by an array of software tools. 1.1 document purpose this datasheet contains information about the product name device family. throughout this document, this device family is referred to as the w30 flash memory device. ? this chapter provides a flash memory overview. ? chapter 2.0 through chapter 8.0 describe the memory functionality. ? chapter 6.0 describes the electrical specifications for extended temperature product offerings. ? appendix a describes the write state machine (wsm), ? appendix b describes the numonyx? common flash interface (cfi) as it applies to the w30 flash memory device. ? appendix c provides ordering information for the product name device family. 1.2 nomenclature acronyms that describe product features or usage are defined here: ? aps - automatic power savings ? bba - block base address ? cfi - common flash interface ? cui - command user interface ? du - do not use ? efp - enhanced factory programming ? fdi - flash data integrator ? nc - no connect ? otp - one-time programmable ? pba - partition base address ? rcr - read configuration register
numonyx? wireless flash memory (w30) datasheet november 2007 8 order number: 290702-13 numonyx? wireless flash memory (w30) ? rwe - read-while-erase ? rww - read-while-write ? scsp - stacked chip scale package ? srd - status register data ? vf bga - very-thin, fine-pitch, ball grid array ? wsm - write state machine 1.3 conventions the following abbreviated terms and phrases are used throughout this document: ? 1.8 v refers to the v cc operating voltage range of 1.7 v ? 1.9 v (except where noted). ? 3.0 v refers to the v ccq operating voltage range of 2.2 v - 3.3 v. ? v pp =12v refers to 12 v 5%. ? when referring to registers, the term set means the bit is a logical 1, and cleared means the bit is a logical 0. ?the terms pin and signal are often used interchangeably to refer to the external signal connections on the package. ( ball is the term used for bga). ?a word is 2 bytes, or 16 bits. ? signal names are in all caps (for example, wait). ? voltage applied to the signal is subscripted (for example, v pp ). throughout this document, references are made to top, bottom, parameter, and partition. to clarify these references, the following conventions have been adopted: ?a block is a group of bits (or words) that erase simultaneously with one block erase instruction. ?a main block contains 32 kwords. ?a parameter block contains 4 kwords. ?the block base address (bba) is the first address of a block. ?a partition is a group of blocks that share erase and program circuitry and a common status register. ?the partition base address (pba) is the first address of a partition. for example, on a 32-mbit top-parameter flash device, partition number 5 has a pba of 0x140000. ?the top partition is located at the highest physical flash device address. this partition can be a main partition or a parameter partition. ?the bottom partition is located at the lowest physical flash device address. this partition can be a main partition or a parameter partition. ?a main partition contains only main blocks. ?a parameter partition contains a mixture of main blocks and parameter blocks. ?a top parameter device ( tpd ) has the parameter partition at the top of the memory map with the parameter blocks at the top of that partition. this flash device type was formerly referred to as a top-boot flash device. ?a bottom parameter device ( bpd ) has the parameter partition at the bottom of the memory map with the parameter blocks at the bottom of that partition. this flash device type was formerly referred to as a bottom-boot block flash device.
november 2007 datasheet order number: 290702-13 9 numonyx? wireless flash memory (w30) 2.0 functional overview this section provides an overview of the w30 flash memory device features and architecture. 2.1 overview the w30 flash memory device provides read-while-write (rww) and read-white- erase (rwe) capability. this capability provides high-performance synchronous and asynchronous reads in package-compatible densities using a 16-bit data bus. individually-erasable memory blocks are optimally sized for code and data storage. eight 4-kword parameter blocks are located in the parameter partition at either the top or bottom of the memory map. the rest of the memory array is grouped into 32-kword main blocks. the memory architecture for the w30 flash memory device consists of multiple 4-mbit partitions, the exact number depending on the flash device density. by dividing the memory array into partitions, program or erase operations can take place simultaneously during read operations. burst reads can traverse partition boundaries, but user application code is responsible for ensuring that burst reads do not extend into a partition that is actively programming or erasing. although each partition has burst- read, write, and erase capabilities, simultaneous operation is limited to write or erase in one partition while other partitions are in a read mode. augmented erase-suspend functionality further enhances the rww capabilities of the w30 flash memory device. an erase can be suspended to perform a program or read operation within any block, except a block that is erase-suspended. a program operation nested within a suspended erase can subsequently be suspended to read yet another memory location. after power-up or reset, the w30 flash memory device defaults to asynchronous read configuration. writing to the flash memory device read configuration register (rcr) enables synchronous burst-mode read operation. in synchronous mode, the clk input increments an internal burst address generator. clk also synchronizes the flash memory device with the host cpu and outputs data on every, or on every other, valid clk cycle after an initial latency. a programmable wait output signals to the cpu when data from the flash memory device is ready. in addition to its improved architecture and interface, the w30 flash memory device incorporates enhanced factory programming (efp), a feature that enables fast programming and low-power designs. the efp feature provides fast program performance, which can increase the manufacturing throughput of a factory. the w30 flash memory device supports read operations at 1.8 v and erase and program operations at 1.8 v or 12 v. with the 1.8-v option, vcc and vpp can be tied together for an ultra-low-power design. in addition to voltage flexibility, the dedicated vpp input provides extensive data protection when v pp < v pplk . a 128-bit protection register can implement new security techniques and data protection schemes: ? a combination of factory-programmed and user-otp data cells provide unique flash device identification, help implement fraud or cloning prevention schemes, or help protect content. ? zero-latency locking/unlocking on any memory block provides instant and complete protection for critical system code and data. ? an additional block lock-down capability provides hardware protection where software commands alone cannot change the block protection status.
numonyx? wireless flash memory (w30) datasheet november 2007 10 order number: 290702-13 numonyx? wireless flash memory (w30) the flash device command user interface (cui) links the system processor to the internal flash memory operation. a valid command sequence written to the cui initiates the flash device write state machine (wsm) operation, which automatically executes the algorithms, timings, and verifications necessary to manage flash memory program and erase. an internal status register provides ready/busy indication results of the operation (success, fail, and so on). three power-saving features? automatic power savings (aps), standby, and rst#? can significantly reduce power consumption. ? the flash device automatically enters aps mode following read cycle completion. ? standby mode begins when the system deselects the flash memory by de-asserting ce#. ? driving rst# low produces power savings similar to standby mode. it also resets the part to read-array mode (important for system-level reset), clears internal status registers, and provides an additional level of flash device write protection. 2.2 memory map and partitioning the w30 flash memory device is divided into 4-mbit physical partitions. this partitioning allows simultaneous rww or rwe operations, and enables users to segment code and data areas on 4-mbit boundaries. the flash memory array is asymmetrically blocked, which enables system code and data integration within a single flash device. each block can be erased independently in block erase mode. simultaneous program and erase operations are not allowed; only one partition at a time can be actively programming or erasing. see table 1, ?bottom parameter memory map? on page 11 and table 2, ?top parameter memory map? on page 11 . ? the 32-mbit flash device has eight partitions. ? the 64-mbit flash device has 16 partitions. ? the 128-mbit flash device has 32 partitions. each flash device density contains one parameter partition and several main partitions. the 4-mbit parameter partition contains eight 4-kword parameter blocks and seven 32- kword main blocks. each 4-mbit main partition contains eight 32-kword blocks. the bulk of the flash memory array is divided into main blocks that can store code or data, and parameter blocks that allow storage of frequently updated small parameters that are normally stored in eeprom. by using software techniques, the word-rewrite functionality of eeproms can be emulated. .
november 2007 datasheet order number: 290702-13 11 numonyx? wireless flash memory (w30) . table 1: bottom parameter memory map size (kw) blk # 32 mbit blk # 64 mbit blk # 128 mbit main partitions sixteen partitions 32 262 7f8000-7fffff .. . .. . .. . 32 135 400000-407fff eight partitions 32 134 3f8000-3fffff 134 3f8000-3fffff .. . .. . .. . .. . .. . 32 71 200000-207fff 71 200000-207fff four partitions 32 70 1f8000-1fffff 70 1f8000-1fffff 70 1f8000-1fffff .. . .. . .. . .. . .. . .. . .. . 32 39 100000-107fff 39 100000-107fff 39 100000-107fff one partition 32 38 0f8000-0fffff 38 0f8000-0fffff 38 0f8000-0fffff .. . .. . .. . .. . .. . .. . .. . 32 31 0c0000-0c7fff 31 0c0000-0c7fff 31 0c0000-0c7fff one partition 32 30 0b8000-0bffff 30 0b8000-0bffff 30 0b8000-0bffff .. . .. . .. . .. . .. . .. . .. . 32 23 080000-087fff 23 080000-087fff 23 080000-087fff one partition 32 22 078000-07ffff 22 078000-07ffff 22 078000-07ffff .. . .. . .. . .. . .. . .. . .. . 32 15 040000-047fff 15 040000-047fff 15 040000-047fff parameter one partition 32 14 038000-03ffff 14 038000-03ffff 14 038000-03ffff .. . .. . .. . .. . .. . .. . .. . 32 8 008000-00ffff 8 008000-00ffff 8 008000-00ffff 4 7 007000-007fff 7 007000-007fff 7 007000-007fff .. . .. . .. . .. . .. . .. . .. . 4 0 000000-000fff 0 000000-000fff 0 000000-000fff table 2: top parameter memory map size (kw) blk # 32 mbit blk # 64 mbit blk # 128 mbit parameter partition one partition 4 70 1ff000-1fffff 134 3ff000-3fffff 262 7ff000-7fffff .. . .. . .. . .. . .. . .. . .. . 4 63 1f8000-1f8fff 127 3f8000-3f8fff 255 7f8000-7f8fff 32 62 1f0000-1f7fff 126 3f0000-3f7fff 254 7f0000-7f7fff .. . .. . .. . .. . .. . .. . .. . 32 56 1c0000-1c7fff 120 3c0000- 3c7fff 248 7c0000-7c7fff
numonyx? wireless flash memory (w30) datasheet november 2007 12 order number: 290702-13 numonyx? wireless flash memory (w30) main partitions one partition 32 55 1b8000-1bffff 119 3b8000-3bffff 247 7b8000-7bffff .. . .. . .. . .. . .. . .. . .. . 32 48 18000-187fff 112 380000-387fff 240 780000-787fff one partition 32 47 178000-17ffff 111 378000-37ffff 239 778000-77ffff .. . .. . .. . .. . .. . .. . .. . 32 40 140000-147fff 104 340000-347fff 232 740000-747fff one partition 32 39 138000-13ffff 103 338000-33ffff 231 738000-73ffff .. . .. . .. . .. . .. . .. . .. . 32 32 100000-107fff 96 300000-307fff 224 700000-707fff four partitions 32 31 0f8000-0fffff 95 2f8000-2fffff 223 6f8000-6fffff .. . .. . .. . .. . .. . .. . .. . 32 0 000000-007fff 64 200000-207fff 192 600000-607fff eight partitions 32 63 1f8000-1fffff 191 5f8000-5fffff .. . .. . .. . .. . .. . 32 0 000000-007fff 128 400000-407fff sixteen partitions 32 127 3f8000-3fffff .. . .. . .. . 32 0 000000-007fff table 2: top parameter memory map size (kw) blk # 32 mbit blk # 64 mbit blk # 128 mbit
november 2007 datasheet order number: 290702-13 13 numonyx? wireless flash memory (w30) 3.0 package information 3.1 w30 flash memory device ? 130 nm lithography figure 1: 32 mb, 64 mb, and 128 mb vf bga package drawing table 3: 2 mb, 64 mb, and 128 mb vf bga package specifications dimension symbol millimeters inches min nom max min nom max package height a - - 1.000 - - 0.0394 ball height a 1 0.150 - - 0.0059 - - package body thickness a 2 - 0.665 - - 0.0262 - ball (lead) width b 0.325 0.375 0.425 0.0128 0.0148 0.0167 package body width (32 mb, 64 mb) d 7.600 7.700 7.800 0.2992 0.3031 0.3071 package body width (128 mb) d 10.900 11.000 11.10 0 0.4291 0.4331 0.4370 package body length (32 mb, 64 mb, 128 mb) e 8.900 9.000 9.100 0.3504 0.3543 0.3583 pitch [e] - 0.750 - - 0.0295 - ball (lead) count n - 56 - - 56 - seating plane coplanarity y - - 0.100 - - 0.0039 corner to ball a1 distance along d (32 mb, 64 mb) s 1 1.125 1.225 1.325 0.0443 0.0482 0.0522 corner to ball a1 distance along d (128 mb) s 1 2.775 2.2875 2.975 0.1093 0.1132 0.1171 corner to ball a1 distance along e (32 mb, 64 mb,128 mb) s 2 2.150 2.250 2.350 0.0846 0.0886 0.0925 e seating plane top view - bump side down bot t om vie w - ball sid e up y a a1 d a2 2 ball a1 cor ne r 87654321 a b c d e f g s 1 s e b ball a1 corner 8 7 6 5 4 3 2 1 a b c d e f g
numonyx? wireless flash memory (w30) datasheet november 2007 14 order number: 290702-13 numonyx? wireless flash memory (w30) figure 2: 32mb, 64mb and 128mb quad+ package drawing millimeters inches dimens ions symbol min nom max notes min nom max package height a 1.200 0.0472 ball height a1 0.200 0.0079 package body thickness a2 0.860 0.0339 ball (lead) width b 0.325 0.375 0.425 0.0128 0.0148 0.0167 package body length d 9.900 10.000 10.100 0.3898 0.3937 0.3976 package body width e 7.900 8.000 8.100 0.3110 0.3150 0.3189 pitch e 0.800 0.0315 ball (lead) cou nt n 88 88 seating plane coplanarity y 0.100 0.0039 corner to ball a1 dis tance along e s1 1.100 1.200 1.300 0.0433 0.0472 0.0512 corner to ball a1 dis tance along d s2 0.500 0.600 0.700 0.0197 0.0236 0.0276 top view - ball down bottom view - ball up a a2 d e y a1 drawing not to scale. s2 s1 a c b e d g f j h k l m e 1 2 3 4 5 6 7 8 b a c b e d g f j h k l m a1 index mark 12345678
november 2007 datasheet order number: 290702-13 15 numonyx? wireless flash memory (w30) 3.2 w30 flash memory device ? 180 nm lithography figure 3: 64mb ?|?? ?? ??? ????? ? ????????? a 2 bottom view - bump side up top view - silicon backside com p lete ink mark not side a a 1 seati plan y s 2 pin # 1 indicator e b pin # 1 corner s 1 e d 1 2 3 4 5 6 7 8 a b c d e f g 8 7 6 5 4 3 2 1 a b c d e f g millimeters inches symbol min nom max notes min nom max package height a 0.850 1.000 0.0335 0.0394 ball height a1 0.150 0.0059 package body thickness a2 0.612 0.712 0.812 0.0241 0.0280 0.0320 ball (lead) width b 0.300 0.350 0.400 0.0118 0.0138 0.0157 package body width d 7.600 7.700 7.800 0.2992 0.3031 0.3071 package body length e 8.900 9.000 9.100 0.3503 0.3543 0.3583 pitch [e] 0.750 0.0295 ball (lead) count n 56 56 seating plane coplanarity y 0.100 0.0039 corner to ball a1 distance along d s1 1.125 1.225 1.325 0.0443 0.0482 0.0522 corner to ball a1 distance along e s2 2.150 2.250 2.350 0.0846 0.0886 0.0925
numonyx? wireless flash memory (w30) datasheet november 2007 16 order number: 290702-13 numonyx? wireless flash memory (w30) figure 4: 32mb vf bga package drawing figure 5: 128mb vf bga package drawing e seating plane top view - bump side down bottom view - ball side up y a a1 d a2 2 ball a1 corne r s 1 s e b ba l l a1 corner a b c d e f g 8 7 6 5 4 3 2 1 87654321 a b c d e f g note: drawin g not to scale side view seating plane y a a1 a2 note: drawin g not to scal e side view e top view - bump side down bottom view - ball side up d ball a 1 corne r s1 s2 e b 7654321 10 9 8 a b c d e f g h j 7 6 5 4 3 2 110 9 8 a b c d e f g h j ball a1 corner
november 2007 datasheet order number: 290702-13 17 numonyx? wireless flash memory (w30) table 4: 32mb and 128mb vf bga package dimensions dimension symbol millimeters inches min nom max min nom max package height a 0.850 - 1.000 0.0335 - 0.0394 ball height a 1 0.150 - - 0.0059 - - package body thickness a 2 0.615 0.665 0.715 0.0242 0.0262 0.0281 ball (lead) width b 0.325 0.375 0.425 0.0128 0.0148 0.0167 package body width 32mb d 7.600 7.700 7.800 0.2992 0.3031 0.3071 package body length32mb e 8.900 9.000 9.100 0.3503 0.3543 0.3583 package body width 128mb d 12.400 12.500 12.600 0.4882 0.4921 0.4961 package body length 128mb e 11.900 12.000 12.100 0.4685 0.4724 0.4764 pitch [e] - 0.750 - - 0.0295 - ball (lead) count 32mb n - 56 - - 56 - ball (lead) count 128mb n - 60 - - 60 - seating plane coplanarity y - - 0.100 - - 0.0039 corner to ball a1 distance along d 32mb s 1 1.125 1.225 1.325 0.0443 0.0482 0.0522 corner to ball a1 distance along e 32mb s 2 2.150 2.250 2.350 0.0846 0.0886 0.0925 corner to ball a1 distance along d 128mb s 1 2.775 2.875 2.975 0.1093 0.1132 0.1171 corner to ball a1 distance along e 128mb s 2 2.900 3.000 3.1000 0.1142 0.1181 0.1220
numonyx? wireless flash memory (w30) datasheet november 2007 18 order number: 290702-13 numonyx? wireless flash memory (w30) 4.0 ballout and signal descriptions 4.1 signal ballout the w30 flash memory device is available in the 56-ball vf bga and bga chip scale package with 0.75 mm ball pitch, or the quad+ scsp package. figure 6 shows the vf bga and bga package ballout. figure 7 shows the quad+ package ballout. notes: 1. on lower density flash memory devices, the upper address balls can be treated as nc. (that is, on 32-mbit density, a22 and a21 are nc). 2. see appendix c, ?ordering information? on page 99 for mechanical specifications for the package. figure 6: 56-ball vf bga/ bga ballout a b c d e f g a b c d e f g top view - ball side down complete ink mark not shown 8 7 6 5 4 3 2 1 1 2 3 4 5 6 7 8 bottom view - ball side up a4 a6 a18 vpp vcc vss a8 a11 a3 a5 a17 rst# clk a20 a9 a12 a2 a7 we# adv# a19 a10 a13 a1 a14 wp# dq12 a16 wait a15 a0 ce# dq1 dq2 dq4 dq6 dq15 vccq oe# dq0 dq9 dq10 dq11 dq13 dq14 vss vssq dq8 vccq dq3 vcc dq5 vssq dq7 a22 a21 a4 a6 a18 vpp vcc vss a8 a11 a3 a5 a17 rst# clk a20 a9 a12 a2 a7 we# adv# a19 a10 a13 a1 a14 wp# dq12 a16 wait a15 a0 ce# dq1 dq2 dq4 dq6 dq15 vccq oe# dq0 dq9 dq10 dq11 dq13 dq14 vss vssq dq8 vccq dq3 vcc dq5 vssq dq7 a22 a21
november 2007 datasheet order number: 290702-13 19 numonyx? wireless flash memory (w30) notes: 1. on lower density flash memory devices, the upper address balls can be treated as nc (that is, on 64-mb density, a[25:23]are nc) 2. see appendix c, ?ordering information? on page 99 for mechanical specifications for the package. figure 7: 88-ball (80 active balls) quad+ ballout flash specific sram/psram specific global legend: top view - ball side down 8 7 6 5 4 3 2 1 a b c d e f g h j k l m du a4 du du du du du du du a5 a3 a2 a7 a1 a6 a0 a18 a19 vss vss a23 a24 a25 a17 f2-vcc clk a21 a22 a12 a11 a13 a9 p1-cs# f-vpp, f-vpen a20 a10 a15 f-we# a8 d8 d2 d10 d5 d13 wait a14 a16 f1-ce# p-mode, p-cre vss vss vss p2-cs# f1-vcc f2-vcc vccq f3-ce# d0 d1 d9 d3 d4 d6 d7 d15 d11 d12 d14 f1-oe# f2-oe# p-vcc s-cs2 r-we# r-ub# r-lb# r-oe# s-vcc s-cs1# f1-vcc f-wp# adv# f-rst# f2-ce# vccq vss vss vccq vss
numonyx? wireless flash memory (w30) datasheet november 2007 20 order number: 290702-13 numonyx? wireless flash memory (w30) 4.2 signal descriptions ? ta b l e 5 describes the signals for the 56-ball vf bga and bga chip scale package. ? ta b l e 6 describes the signals for the quad+ package ballout. table 5: signal descriptions - bga package & vf bga package symbol type name and function a[22:0] input address inputs: for memory addresses. 32 mbit: a[20:0]; 64 mbit: a[21:0]; 128 mbit: a[22:0] d[15:0] input/ output data inputs/outputs: ? inputs data and commands during write cycles. ? outputs data during reads. data pins are high-z when the flash device or its outputs are deselected. data is internally latched during writes. adv# input address valid: adv# indicates valid address presence on address inputs. during synchronous read operations, all addresses are latched on the rising edge of adv#, or the next valid clk edge with adv# low, whichever occurs first. ce# input chip enable: ? asserting ce# activates internal control logic, i/o buffers, decoders, and sense amps. ? de-asserting ce# deselects the flash device, places it in standby mode, and tri-states all outputs. clk input clock: clk synchronizes the flash device to the system bus frequency during synchronous reads and increments an internal address generator. during synchronous read operations, addresses are latched on adv#?s rising edge or clk?s rising (or falling) edge, whichever occurs first. oe# input output enable: ? when asserted, oe# enables the flash device output data buffers during a read cycle. ? when oe# is deasserted, data outputs are placed in a high-impedance state. rst# input reset: when low, rst# resets internal automation and inhibits write operations. this reset provides data protection during power transitions. de-asserting rst# enables normal operation and places the flash device in asynchronous read-array mode. wait output wait: the wait signal indicates valid data during synchronous read modes. it can be configured to be asserted-high or asserted-low, based on bit 10 of the read configuration register. wait is tri- stated if ce# is deasserted. wait is not gated by oe#. we# input write enable: we# controls writes to the cui and array. addresses and data are latched on the rising edge of we#. wp# input write protect: disables/enables the lock-down function. when wp# is asserted, the lock-down mechanism is enabled and blocks marked lock-down cannot be unlocked through software. see section 13.1, ?block lock operations? on page 71 for details on block locking. vpp power/ input erase and program power: a valid voltage on this pin allows erasing or programming. flash memory contents cannot be altered when v pp < v pplk . do not attempt block erase and program operations at invalid v pp voltages. set v pp = v cc for in-system program and erase operations. to accommodate resistor or diode drops from the system supply, the v ih level of v pp can be as low as v ppl min. v pp must remain above v ppl min to perform in-system flash device modification. vpp can be 0 v during read operations. v pph can be applied to main blocks for 1000 cycles maximum and to parameter blocks for 2500 cycles. vpp can be connected to 12 v for a cumulative total not to exceed 80 hours. extended use of this pin at 12 v might reduce block cycling capability. vcc power flash device power supply: writes are inhibited at v cc < v lko . do not attempt flash device operations at invalid v cc voltages. vccq power output power supply: enables all outputs to be driven at v ccq . vss power ground: pins for all internal flash device circuitry must be connected to system ground. vssq power output ground : provides ground to all outputs which are driven by vccq. this signal can be tied directly to vss. du ? do not use: do not use this pin. do not connect this pin to any power supplies, signals, or other pins; this pin must be floated. nc ? no connect: no internal connection; can be driven or floated.
november 2007 datasheet order number: 290702-13 21 numonyx? wireless flash memory (w30) table 6: signal descriptions - quad+ package (sheet 1 of 3) symbol type description a[max:min] input address inputs: inputs for all die addresses during read and write operations. ? 128-mbit die : amax = a22 ? 64-mbit die : amax = a21 ? 32-mbit die : amax = a20 a0 is the lowest-order 16-bit wide address. a[25:24] denote high-order addresses reserved for future flash device densities. dq[15:0] input/ output data inputs/outputs: ? inputs data and commands during write cycles. ? outputs data during read cycles. data signals float when the flash device or its outputs are deselected. data are internally latched during writes on the flash device. f[3:1]-ce# input flash chip enable: low-true input. f[3:1]-ce# low selects the associated flash memory die. ? when asserted, flash memory internal control logic, input buffers, decoders, and sense amplifiers are active. ? when deasserted, the associated flash die is deselected, power is reduced to standby levels, and data and wait outputs are placed in high-z state. ? f1-ce# selects or deselects flash die #1. ? f2-ce# selects or deselects flash die #2 and is rfu on combinations with only one flash die. ? f3-ce# selects or deselects flash die #3 and is rfu on stacked combinations with only one or two flash dies. s-cs1# s-cs2 input sram chip select: low-true / high-true input (s-cs1# / s-cs2 respectively). ? when either/both sram chip select signals are asserted, sram internal control logic, input buffers, decoders, and sense amplifiers are active. ? when either/both sram chip select signals are deasserted, the sram is deselected and its power is reduced to standby levels. s-cs1# and s-cs2 are available on stacked combinations with sram die and are rfu on stacked combinations without sram die. p[2:1]-cs# input psram chip select: low-true input. ? when asserted, psram internal control logic, input buffers, decoders, and sense amplifiers are active. ? when deasserted, the psram is deselected and its power is reduced to standby levels. ? p1-cs# selects psram die #1 and is available only on stacked combinations with psram die. this ball is an rfu on stacked combinations without psram. ? p2-cs# selects psram die #2 and is available only on stacked combinations with two psram dies. this ball is an rfu on stacked combinations without psram or with a single psram. f[2:1]-oe# input flash output enable: low-true input. ? fx-oe# low enables the output buffers on the selected flash memory device. ? f[2:1]-oe# high disables the output buffers on the selected flash memory device, placing them in high-z. ? f1-oe# controls the outputs of flash die #1. ? f2-oe# controls the outputs of flash die #2 and flash die #3. f2-oe# is available on stacked combinations with two or three flash die, and is rfu on stacked combinations with only one flash die. r-oe# input ram output enable: low-true input. ? r-oe# low enables the output buffers on the selected ram. ? r-oe# high disables the ram output buffers, and places the selected ram outputs in high-z. r-oe# is available on stacked combinations with psram or sram die, and is an rfu on flash-only stacked combinations. f-we# input flash write enable: low-true input. f-we# controls writes to the selected flash die. address and data are latched on the rising edge of f-we#.
numonyx? wireless flash memory (w30) datasheet november 2007 22 order number: 290702-13 numonyx? wireless flash memory (w30) r-we# input ram write enable: low-true input. r-we# controls writes to the selected ram die. r-we# is available on stacked combinations with psram or sram die, and is an rfu on flash-only stacked combinations. clk input clock: synchronizes the flash die with the system bus clock in synchronous read mode and increments the internal address generator. ? during synchronous read operations, addresses are latched on the rising edge of adv#, or on the next valid clk edge with adv# low, whichever occurs first. ? during asynchronous mode read operations, addresses are latched on the rising edge adv#, or are continuously flow-through when adv# is kept asserted. wait output wait: output signal. indicates invalid data during synchronous array or non-array flash memory reads. read configuration register bit 10 (rcr[10]) determines wait-asserted polarity (high or low). wait is high-z if f-ce# is deasserted; wait is not gated by f-oe#. ? in synchronous array or non-array flash memory read modes, wait indicates invalid data when asserted and valid data when deasserted. ? in asynchronous flash memory page read, and all flash memory write modes, wait is asserted. f-wp# input flash write protect: low-true input. f-wp# enables/disables the lock-down protection mechanism of the selected flash die. ? f-wp# low enables the lock-down mechanism where locked down blocks cannot be unlocked using software commands. ? f-wp# high disables the lock-down mechanism, allowing locked down blocks to be unlocked using software commands. adv# input address valid: low-true input. ? during synchronous flash memory read operations, addresses are latched on the rising edge of adv#, or on the next valid clk edge with adv# low, whichever occurs first. ? during asynchronous flash memory read operations, addresses are latched on the rising edge of adv#, or are continuously flow-through when adv# is kept asserted. r-ub# r-lb# input ram upper / lower byte enables: low-true input. during ram read and write cycles: ? r-ub# low enables the ram high order bytes on d[15:8]. ? r-lb# low enables the ram low-order bytes on d[7:0]. r-ub# and r-lb# are available on stacked combinations with psram or sram die, and are rfu on flash-only stacked combinations. f-rst# input flash reset: low-true input. ? f-rst# low initializes flash device internal circuitry and disables flash device operations. ? f-rst# high enables flash device operation. exit from reset places the flash device in asynchronous read array mode. p-mode, p-cre input p-mode (psram mode): low-true input. p-mode programs the configuration register, and enters/exits the low power mode of the psram die. p-mode is available on stacked combinations with asynchronous-only psram die. ? p-cre (psram configuration register enable): high-true input. ? p-cre is high, write operations load the refresh control register or bus control register. ? p-cre applies only on combinations with synchronous psram die. p-mode, p-cre is an rfu on stacked combinations without psram die. f-vpp, f-vpen power flash program and erase power: valid f-v pp voltage on this ball enables flash memory device program/erase operations. flash memory array contents cannot be altered when f-v pp (f-v pen ) < v pplk (v penlk ). do not attempt erase / program operations at invalid f-v pp (f-v pen ) voltages. f-vpen (erase/program/block lock enables) is not available for l18/l30 scsp products. table 6: signal descriptions - quad+ package (sheet 2 of 3) symbol type description
november 2007 datasheet order number: 290702-13 23 numonyx? wireless flash memory (w30) f[2:1]-vcc power flash logic power: ? f1-vcc supplies power to the core logic of flash die #1. ? f2-vcc supplies power to the core logic of flash die #2 and flash die #3. write operations are inhibited when f-v cc < v lko . do not attempt flash device operations at invalid f-v cc voltages. f2-vcc is available on stacked combinations with two or three flash dies, and is an rfu on stacked combinations with only one flash die. s-vcc power sram power supply: supplies power for sram operations. s-vcc is available on stacked combinations with sram die, and is rfu on stacked combinations without sram die. p-vcc power psram power supply: supplies power for psram operations. p-vcc is available on stacked combinations with psram die, and is rfu on stacked combinations without psram die. vccq power flash device i/o power: supply power for the flash device input and output buffers. vss power flash device ground: connect to system ground. do not float any vss connection. rfu ? reserved for future use: reserved for future flash device functionality/ enhancements. contact numonyx regarding the use of balls designated rfu. du ? do not use: do not connect to any other signal, or power supply; must be left floating. table 6: signal descriptions - quad+ package (sheet 3 of 3) symbol type description
numonyx? wireless flash memory (w30) datasheet november 2007 24 order number: 290702-13 numonyx? wireless flash memory (w30) 5.0 maximum ratings and operating conditions 5.1 absolute maximum ratings warning: stressing the flash device beyond the absolute maximum ratings in ta b l e 7 might cause permanent damage. these are stress ratings only. 5.2 operating conditions do not operate the w30 flash memory device beyond the operating conditions in ta b l e 8 . extended exposure beyond these operating conditions might affect flash device reliability. notice: this datasheet contains information on products in the design phase of development. the information here is subject to change without notice. do not finalize a design with this information. table 7: absolute maximum ratings parameter maximum rating note temperature under bias ?40 c to +85 c storage temperature ?65 c to +125 c voltage on any pin (except v cc , v ccq , v pp ) ?0.5 v to +3.8 v v pp voltage ?0.2 v to +14 v 1 , 2 , 3 v cc voltage ?0.2 v to +2.45 v 1 v ccq voltage ?0.2 v to +3.8 v 1 output short circuit current 100 ma 4 notes: 1. all specified voltages are relative to v ss . minimum dc voltage is ?0.5 v on input/output pins and ?0.2 v on v cc and v pp pins. during transitions, this level might undershoot to ?2.0 v for periods < 20 ns. maximum dc voltage on input/output pins is v cc +0.5 v which, during transitions, might overshoot to v cc +2.0 v for periods < 20 ns. 2. maximum dc voltage on v pp might overshoot to +14.0 v for periods < 20 ns. 3. v pp program voltage is normally v ppl . v pp can be 12 v 0.6 v for 1000 cycles on the main blocks and 2500 cycles on the parameter blocks during program/erase. 4. output shorted for no more than one second. no more than one output shorted at a time. table 8: extended temperature operation (sheet 1 of 2) symbol parameter 1 min nom max unit notes t a operating temperature ?40 25 85 c - v cc v cc supply voltage 1.7 1.8 1.90 v 3 v ccq i/o supply voltage 2.2 3.0 3.3 3 v ppl v pp voltage supply (logic level) 0.90 1.80 1.95 2 v pph factory programming v pp 11.4 12.0 12.6 2 t pph maximum v pp hours v pp = 12 v - - 80 hours 2
november 2007 datasheet order number: 290702-13 25 numonyx? wireless flash memory (w30) block erase cycles main and parameter blocks v pp < v cc 100,000 - - cycles 2 main blocks v pp = 12 v - - 1000 2 parameter blocks v pp = 12 v - - 2500 2 notes: 1. see section 6.1, ?dc current characteristics? on page 26 and section 6.2, ?dc voltage characteristics? on page 27 for specific voltage-range specifications. 2. vpp is normally v ppl . vpp can be connected to 11.4 v?12.6 v for 1000 cycles on main blocks for extended temperatures and 2500 cycles on parameter blocks at extended temperature. 3. contact your numonyx field representative for v cc /v ccq operations down to 1.65 v. 4. see the tables in section 6.0, ?electrical specifications? on page 26 and in section 7.0, ?ac characteristics? on page 28 for operating characteristics table 8: extended temperature operation (sheet 2 of 2) symbol parameter 1 min nom max unit notes
numonyx? wireless flash memory (w30) datasheet november 2007 26 order number: 290702-13 numonyx? wireless flash memory (w30) 6.0 electrical specifications 6.1 dc current characteristics table 9: dc current characteristics (sheet 1 of 2) sym parameter (1) note v ccq = 3.0 v uni t test conditions 32/64 mbit 128 mbit typ max typ max i li input load 9 - 2 - 2 a v cc = v cc max v ccq = v ccq max v in = v ccq or gnd i lo output leakage dq[15:0] - 10 - 10 a v cc = v cc max v ccq = v ccq max v in = v ccq or gnd 180 nm i ccs v cc standby 10 621630 a v cc = v cc max v ccq = v ccq max ce# = v ccq rst# =v ccq 130 nm i ccs 850870 180 nm i ccaps aps 11 621630 a v cc = v cc max v ccq = v ccq max ce# = v ssq rst# =v ccq all other inputs =v ccq or v ssq 130 nm i ccaps 850870 i ccr average v cc read asynchronous page mode f=13 mhz 2 4 7 4 10 ma 4 word read v cc = v cc max ce# = v il oe# = v ih inputs = v ih or v il synchronous clk = 40 mhz 2 7 15 7 15 ma burst length = 4 9 16 9 16 ma burst length = 8 11 19 11 19 ma burst length =16 12 22 12 22 ma burst length = continuous i ccw v cc program 3,4,5 18 40 18 40 ma v pp = v ppl, program in progress 815815ma v pp = v pph, program in progress i cce v cc block erase 3,4,5 18 40 18 40 ma v pp = v ppl, block erase in progress 815815ma v pp = v pph, block erase in progress i ccws v cc program suspend 6 621630a ce# = v cc, program suspended i cces v cc erase suspend 6 621630a ce# = v cc, erase suspended i pps (i ppws, i ppes ) v pp standby v pp program suspend v pp erase suspend 3 0.250.25av pp < v cc i ppr v pp read - 215215a v pp < v cc i ppw v pp program 4 0.05 0.10 0.05 0.10 ma v pp = v ppl, program in progress 8 221637 v pp = v pph, program in progress
november 2007 datasheet order number: 290702-13 27 numonyx? wireless flash memory (w30) 6.2 dc voltage characteristics i ppe v pp erase 4 0.05 0.10 0.05 0.10 ma v pp = v ppl, erase in progress 822822 v pp = v pph, erase in progress notes: 1. all currents are rms unless noted. typical values at typical v cc , t a = +25c. 2. automatic power savings (aps) reduces i ccr to approximately standby levels in static operation. see i ccrq specification for details. 3. sampled, not 100% tested. 4. v cc read + program current is the sum of v cc read and v cc program currents. 5. v cc read + erase current is the sum of v cc read and v cc erase currents. 6. i cces is specified with the flash device deselected. if the flash device is read while in erase suspend, the current is i cces plus i ccr . 7. v pp < v pplk inhibits erase and program operations. do not use v ppl and v pph outside their valid ranges. 8. v il can undershoot to ?0.4v and v ih can overshoot to v ccq +0.4v for durations of 20 ns or less. 9. if v in >v cc the input load current increases to 10 a max. 10. i ccs is the average current measured over any 5ms time interval 5 s after a ce# de-assertion. 11. refer to section section 8.2, ?automatic power savings (aps)? on page 44 for i ccaps measurement details. table 10: dc voltage characteristics sym parameter (1) note v ccq = 3.0 v unit test conditions 32/64 mbit 128 mbit min max min max v il input low 800.400.4v v ih input high - v ccq ? 0.4 v ccq v ccq ? 0.4 v ccq v v ol output low -- 0.1 - 0.1v v cc = v cc min v ccq = v ccq min i ol = 100 a v oh output high - v ccq ? 0.1 - v ccq ? 0.1 -v v cc = v cc min v ccq = v ccq min i oh = ?100 a v pplk v pp lock-out 7- 0.4 - 0.4v v lko v cc lock -1.0 - 1.0 - v v ilkoq v ccq lock - 0.9 - 0.9 - v note: for all numbered note references in this table, refer to the notes in table 9, ?dc current characteristics? on page 26 . table 9: dc current characteristics (sheet 2 of 2) sym parameter (1) note v ccq = 3.0 v uni t test conditions 32/64 mbit 128 mbit typ max typ max
numonyx? wireless flash memory (w30) datasheet november 2007 28 order number: 290702-13 numonyx? wireless flash memory (w30) 7.0 ac characteristics 7.1 read operations - 130 nm lithography table 11: read operations - 130 nm lithography (sheet 1 of 2) # sym parameter 1 32-mbit 64-mbit 128-mbit units notes -70 -85 -70 min max min max min max asynchronous specifications r1 t avav read cycle time 70 - 85 - 70 -ns 6 r2 t avqv address to output valid - 70 - 85 -70ns 6 r3 t elqv ce# low to output valid - 70 - 85 -70ns 6 r4 t glqv oe# low to output valid - 30 - 30 - 30 ns 3 r5 t phqv rst# high to output valid - 150 - 150 - 150 ns - r6 t elqx ce# low to output low-z 0 - 0 - 0 - ns 4 r7 t glqx oe# low to output low-z 0 - 0 - 0 - ns 3,4 r8 t ehqz ce# high to output high-z - 20 - 20 - 20 ns 4 r9 t ghqz oe# high to output high-z - 14 - 14 - 14 ns 3,4 r10 t oh ce# (oe#) high to output low-z 0 - 0 - 0 - ns 3,4 r11 t ehel ce# pulse width high 20 - 20 - 20 - ns 5 r12 t eltv ce# low to wait valid - 20 - 22 - 22 ns 5 r13 t ehtz ce# high to wait high-z - 25 - 25 - 25 ns 4,5 latching specifications r101 t avvh address setup to adv# high 10 - 10 - 12 - ns - r102 t elvh ce# low to adv# high 10 - 10 - 12 - ns - r103 t vlqv adv# low to output valid - 70 85 -70ns 6 r104 t vlvh adv# pulse width low 10 - 10 - 12 - ns - r105 t vhvl adv# pulse width high 10 - 10 - 12 - ns - r106 t vhax address hold from adv# high 9 - 9 - 9 - ns 2 r108 t apa page address access time - 25 - 25 - 25 ns - clock specifications r200 f clk clk frequency - 40 - 33 - 40 mhz - r201 t clk clk period 25 - 30 - 25 - ns - r202 t ch/l clk high or low time 9.5-9.5-9.5- ns - r203 t chcl clk fall or rise time - 3 - 5 - 5 ns -
november 2007 datasheet order number: 290702-13 29 numonyx? wireless flash memory (w30) 7.2 read operations - 180 nm lithography synchronous specifications r301 t avch address valid setup to clk 9 - 9 - 10 - ns - r302 t vlch adv# low setup to clk 10 - 10 - 10 - ns - r303 t elch ce# low setup to clk 9 - 9 - 9 - ns - r304 t chqv clk to output valid - 20 - 22 - 20 ns - r305 t chqx output hold from clk 5 - 5 - 5 - ns - r306 t chax address hold from clk 10 - 10 - 10 - ns 2 r307 t chtv clk to wait valid - 20 - 22 - 22 ns - notes: 1. see figure 22, ?ac input/output reference waveform? on page 46 for timing measurements and maximum allowable input slew rate. 2. address hold in synchronous-burst mode is defined as t chax or t vhax , whichever timing specification is satisfied first. 3. oe# can be delayed by up to t elqv ? t glqv after the falling edge of ce# without impact to t elqv . 4. sampled, not 100% tested. 5. applies only to subsequent synchronous reads. 6. during the initial access of a synchronous burst read, data from the first word might begin to be driven onto the data bus as early as the first clock edge after t avqv . table 12: read operations - 180 nm lithography (sheet 1 of 2) # sym parameter 1 32-mbit 64-mbit 128-mbit units notes -70 -85 -90 min max min max min max asynchronous specifications r1 t avav read cycle time 70 - 85 - 90 -ns 6 r2 t avqv address to output valid - 70 - 85 -90ns 6 r3 t elqv ce# low to output valid - 70 - 85 -90ns 6 r4 t glqv oe# low to output valid - 30 - 30 - 30 ns 3 r5 t phqv rst# high to output valid - 150 - 150 - 150 ns - r6 t elqx ce# low to output low-z 0-0-0-ns 4 r7 t glqx oe# low to output low-z 0-0-0-ns3,4 r8 t ehqz ce# high to output high-z - 20 - 20 - 20 ns 4 r9 t ghqz oe# high to output high-z - 14 - 14 14 ns 3,4 r10 t oh ce# (oe#) high to output low-z 0-0-0-ns3,4 r11 t ehel ce# pulse width high 20 - 20 - 20 - ns 5 r12 t eltv ce# low to wait valid - 20 - 22 - 22 ns 5 r13 t ehtz ce# high to wait high-z - 25 - 25 - 25 ns 4,5 table 11: read operations - 130 nm lithography (sheet 2 of 2) # sym parameter 1 32-mbit 64-mbit 128-mbit units notes -70 -85 -70 min max min max min max
numonyx? wireless flash memory (w30) datasheet november 2007 30 order number: 290702-13 numonyx? wireless flash memory (w30) latching specifications r101 t avvh address setup to adv# high 10 - 10 - 12 - ns - r102 t elvh ce# low to adv# high 10 - 10 - 12 - ns - r103 t vlqv adv# low to output valid - 70 - 85 - 90 ns 6 r104 t vlvh adv# pulse width low 10 - 10 - 12 - ns - r105 t vhvl adv# pulse width high 10 - 10 - 12 - ns - r106 t vhax address hold from adv# high 9 - 9 - 9 - ns 2 r108 t apa page address access time - 25 - 25 - 30 ns - clock specifications r200 f clk clk frequency - 40 - 33 - 33 mhz - r201 t clk clk period 25 - 30 - 30 - ns - r202 t ch/l clk high or low time 9.5 - 9.5 - 9.5 - ns - r203 t chcl clk fall or rise time - 3 5 - 5 ns - synchronous specifications r301 t avch address valid setup to clk 9 - 9 - 10 - ns - r302 t vlch adv# low setup to clk 10 - 10 - 10 - ns - r303 t elch ce# low setup to clk 9 - 9 - 9 - ns - r304 t chqv clk to output valid - 20 - 22 - 22 ns - r305 t chqx output hold from clk 5 - 5 5 - ns - r306 t chax address hold from clk 10 - 10 - 10 - ns 2 r307 t chtv clk to wait valid - 20 - 22 - 22 ns - notes: 1. see figure 22, ?ac input/output reference waveform? on page 46 for timing measurements and maximum allowable input slew rate. 2. address hold in synchronous-burst mode is defined as t chax or t vhax , whichever timing specification is satisfied first. 3. oe# can be delayed by up to t elqv ? t glqv after the falling edge of ce# without impact to t elqv . 4. sampled, not 100% tested. 5. applies only to subsequent synchronous reads. 6. during the initial access of a synchronous burst read, data from the first word might begin to be driven onto the data bus as early as the first clock edge after t avqv . table 12: read operations - 180 nm lithography (sheet 2 of 2) # sym parameter 1 32-mbit 64-mbit 128-mbit units notes -70 -85 -90 min max min max min max
november 2007 datasheet order number: 290702-13 31 numonyx? wireless flash memory (w30) notes: . 1. wait shown asserted (rcr[10]=0) 2. adv# assumed to be driven to vil in this waveform figure 8: asynchronous read operation waveform v ih v il valid address v ih v il v ih v il v ih v il high z v oh v ol valid output v ih v il r1 r2 r3 r4 r5 r7 r10 address [a] ce# [e] oe# [g] we# [w] data [d/q] rst# [p] r8 r9 v oh v ol high z wait [t] high z note 1
numonyx? wireless flash memory (w30) datasheet november 2007 32 order number: 290702-13 numonyx? wireless flash memory (w30) figure 9: latched asynchronous read operation waveform v oh v ol high z valid output v ih v il v ih v il v ih v il valid address v ih v il v ih v il v ih v il data [q] we# [w] oe# [g] ce# [e] a[max:2] [a] adv# [v] rst# [p] r102 r104 r1 r2 r3 r4 r5 r6 r7 r10 r103 r101 r105 r106 a[1:0] [a] v ih v il valid address valid address valid address r8 r9
november 2007 datasheet order number: 290702-13 33 numonyx? wireless flash memory (w30) note: wait shown asserted (rcr[10] = 0). figure 10: page-mode read operation waveform r105 v ih v il v ih v il v ih v il v ih v il v oh v ol high z valid output valid output valid output valid output v ih v il v ih v il valid address v ih v il valid address valid address valid address valid address r102 r104 adv# [v] ce# [e] oe# [g] we# [w] data [d/q] rst# [p] a[max:2] [a] a[1:0] [a] r1 r2 r101 r106 r103 r3 r4 r7 r6 r108 r10 r5 r9 r8 v oh v ol high z wait [t] high z note 1
numonyx? wireless flash memory (w30) datasheet november 2007 34 order number: 290702-13 numonyx? wireless flash memory (w30) notes: 1. section 14.2, ?first access latency count (rcr[13:11])? on page 80 describes how to insert clock cycles during the initial access. 2. wait (shown asserted; rcr[10]=0) can be configured to assert either during, or one data cycle before, valid data. 3. in this waveform, an x-word burst is initiated to the main array and it is terminated by a ce# de-assertion after the first word in the burst. if this access had been done to status, id, or query reads, the asserted (low) wait signal would have remained asserted (low) as long as ce# is asserted (low). figure 11: single synchronous read-array operation waveform r1 2 r13
november 2007 datasheet order number: 290702-13 35 numonyx? wireless flash memory (w30) notes: 1. section 14.2, ?first access latency count (rcr[13:11])? on page 80 describes how to insert clock cycles during the initial access. 2. wait (shown asserted; rcr[10] = 0) can be configured to assert either during, or one data cycle before, valid data. figure 12: synchronous 4-word burst read operation waveform r12 r11 r13
numonyx? wireless flash memory (w30) datasheet november 2007 36 order number: 290702-13 numonyx? wireless flash memory (w30) notes: 1. section 14.2, ?first access latency count (rcr[13:11])? on page 80 describes how to insert clock cycles during the initial access. 2. wait (shown asserted; rcr[10]=0) can be configured to assert either during, or one data cycle before, valid data. (this example assumes a wait delay of two clocks.) figure 13: wait functionality for eowl (end-of-word line) condition waveform r12
november 2007 datasheet order number: 290702-13 37 numonyx? wireless flash memory (w30) notes: 1. section 14.2, ?first access latency count (rcr[13:11])? on page 80 describes how to insert clock cycles during the initial access. 2. wait shown asserted (rcr[10]=0). figure 14: wait signal in synchronous non-read array operation waveform r12 r13
numonyx? wireless flash memory (w30) datasheet november 2007 38 order number: 290702-13 numonyx? wireless flash memory (w30) note: 1. during burst suspend, the clock signal can be held high or low. 7.3 ac write characteristics figure 15: burst suspend table 13: ac write characteristics (sheet 1 of 2) # sym parameter 1,2 notes 32-mbit 64-mbit 128-mbit unit -70 -85 / -90 min max min max w1 t phwl (t phel ) rst# high recovery to we# (ce#) low 3 150 - 150 - ns w2 t elwl (t wlel ) ce# (we#) setup to we# (ce#) low 0 - 0 - ns w3 t wlwh (t eleh ) we# (ce#) write pulse width low 4 45 - 60 - ns w4 t dvwh (t dveh ) data setup to we# (ce#) high 45 - 60 - ns w5 t avwh (t aveh ) address setup to we# (ce#) high 45 - 60 - ns w6 t wheh (t ehwh ) ce# (we#) hold from we# (ce#) high 0 - 0 - ns w7 t whdx (t ehdx ) data hold from we# (ce#) high 0 - 0 - ns w8 t whax (t ehax ) address hold from we# (ce#) high 0 - 0 - ns w9 t whwl (t ehel )we# (ce#) pulse width high 5 , 6 , 7 25 - 25 - ns w10 t vpwh (t vpeh ) vpp setup to we# (ce#) high 3 200 - 200 - ns w11 t qvvl vpp hold from valid srd 3 , 8 0-0-ns w12 t qvbl wp# hold from valid srd 3 , 8 0-0-ns w13 t bhwh (t bheh ) wp# setup to we# (ce#) high 3 200 - 200 - ns q0 q1 q1 q2 r304 r304 r7 r6 r13 r12 r9 r4 r9 r4 r8 r3 r106 r101 r105 r105 r1 r1 r2 r305 r305 r305 r304 clk address [a] adv# ce# [e] oe# [g] wait [t] we# [w] data [d/q]
november 2007 datasheet order number: 290702-13 39 numonyx? wireless flash memory (w30) w14 t whgl (t ehgl ) write recovery before read - 0 - 0 - ns w16 t whqv we# high to valid data 3, 6 ,1 0 t avqv + 40 - t avqv + 50 -ns w18 t whav we# high to address valid 3, 9 ,1 0 0-0-ns w19 t whcv we# high to clk valid 3, 10 20 - 20 - ns w20 t whvh we# high to adv# high 3, 10 20 - 20 - ns notes: 1. write timing characteristics during erase suspend are the same as during write-only operations. 2. a write operation can be terminated with either ce# or we#. 3. sampled, not 100% tested. 4. write pulse width low (t wlwh or t eleh ) is defined from ce# or we# low (whichever occurs last) to ce# or we# high (whichever occurs first). hence, t wlwh = t eleh = t wleh = t elwh . 5. write pulse width high (t whwl or t ehel ) is defined from ce# or we# high (whichever is first) to ce# or we# low (whichever is last). hence, t whwl = t ehel = t whel = t ehwl . 6. system designers must take this into account, and can insert a software no-op instruction to delay the first read after issuing a command. 7. for commands other than resume commands. 8. v pp must be held at v ppl or v pph until block erase or program success is determined. 9. applicable during asynchronous reads following a write. 10. t whch/l or t whvh must be met when transitioning from a write cycle to a synchronous burst read. t whch/l and t whvh both refer to the address latching event (either the rising/falling clock edge or the rising adv# edge, whichever occurs first). table 13: ac write characteristics (sheet 2 of 2) # sym parameter 1,2 notes 32-mbit 64-mbit 128-mbit unit -70 -85 / -90 minmaxminmax
numonyx? wireless flash memory (w30) datasheet november 2007 40 order number: 290702-13 numonyx? wireless flash memory (w30) notes: 1. v cc power-up and standby. 2. write program or erase setup command. 3. write valid address and data (for program) or erase confirm command. 4. automated program/erase delay. 5. read status register data (srd) to determine program/erase operation completion. 6. oe# and ce# must be asserted and we# must be deasserted for read operations. 7. clk is ignored (but can be kept active/toggling). figure 16: write operations waveform note 1 note 2 note 3 note 4 note 5 address [a] v ih v il valid address valid address ce# (we#) [e(w)] v ih v il note 6 oe# [g] v ih v il we# (ce#) [w(e)] v ih v il rst# [p] v ih v il w6 w7 w8 w11 w12 r105 vpp [v] v pph v pplk v il wp# [b] v ih v il data [q] v ih v il data in valid srd adv# [v] v ih v il w16 w1 w2 w3 w4 w9 w10 w13 w14 r101 r106 data in valid address note 6 r104 w5 w18 w19 w20 clk [c] v ih v il
november 2007 datasheet order number: 290702-13 41 numonyx? wireless flash memory (w30) figure 17: asynchronous read to write operation waveform figure 18: asynchronous write to read operation q d r5 w7 w4 r10 r7 r6 w6 w3 w3 w2 r9 r4 r8 r3 w8 w5 r1 r2 r1 a ddress [a] ce# [e} oe# [g] we# [w] data [d/q] rst# [p] d q w1 r9 r8 r4 r3 r2 w7 w4 w14 w18 w3 w3 r10 w6 w2 r1 r1 w8 w5 a ddress [a] ce# [e} we# [w] oe# [g] data [d/q] rst# [p]
numonyx? wireless flash memory (w30) datasheet november 2007 42 order number: 290702-13 numonyx? wireless flash memory (w30) figure 19: synchronous read to write operation figure 20: synchronous write to read operation latency count q d d w7 r13 r305 r304 r7 r307 r12 w15 w9 w19 w8 w9 w3 w3 w2 r8 r4 w6 r11 r11 r303 r3 w20 r104 r104 r106 r102 r105 r105 w18 w5 r101 r2 r306 r302 r301 clk [c] a ddress [a] ad v# [v] ce# [e] oe# [g] we# wait [t] d ata [d /q] lat ency count d q q w1 r304 r305 r304 r3 w7 w4 r307 r12 r4 w18 w19 w3 w3 r11 r303 r11 w6 w2 w20 r104 r106 r104 r306 w8 w5 r302 r301 r2 clk a ddress [ a] adv# ce# [e} we# [w] oe# [g] wait [t] data [d/q] rst# [p]
november 2007 datasheet order number: 290702-13 43 numonyx? wireless flash memory (w30) 7.4 erase and program times table 14: erase and program times operation symbol parameter description 1 notes v ppl v pph unit typ max typ max erasing and suspending erase time w500 ters/pb 4-kword parameter block 2 , 3 0.3 2.5 0.25 2.5 s w501 t ers/mb 32-kword main block 2 , 3 0.7 4 0.4 4 s suspend latency w600 t susp/p program suspend 2 510510s w601 t susp/e erase suspend 2 520520s programming program time w200 tprog/w single word 2 12 150 8 130 s w201 tprog/pb 4-kword parameter block 2 , 3 0.05 .23 0.03 0.07 s w202 tprog/mb 32-kword main block 2 , 3 0.4 1.8 0.24 0.6 s enhanced factory programming 5 program w400 tefp/w single word 4 n/a n/a 3.5 16 s w401 tefp/pb 4-kword parameter block 2 , 3 n/a n/a 15 - ms w402 tefp/mb 32-kword main block 2 , 3 n/a n/a 120 - ms operation latency w403 t efp/setup efp setup - n/a n/a - 5 s w404 t efp/tran program to verify transition - n/a n/a 2.7 5.6 s w405 t efp/verify verify - n/a n/a 1.7 130 s notes: 1. unless noted otherwise, all parameters are measured at t a = +25 c and nominal voltages, and are sampled, not 100% tested. 2. excludes external system-level overhead. 3. exact results might vary based on system overhead. 4. w400-typ is the calculated delay for a single programming pulse. w400-max includes the delay when programming within a new word-line. 5. some efp performance degradation might occur if block cycling exceeds 10.
numonyx? wireless flash memory (w30) datasheet november 2007 44 order number: 290702-13 numonyx? wireless flash memory (w30) 8.0 power and reset specifications product name devices have a layered approach to power savings that can significantly reduce overall system power consumption. ? the aps feature reduces power consumption when the flash device is selected but idle. ? if ce# is deasserted, the memory enters its standby mode, where current consumption is even lower. ? asserting rst# provides current savings similar to standby mode. the combination of these features can minimize memory power consumption, and therefore, overall system power consumption. 8.1 active power with ce# at v il and rst# at v ih , the flash device is in the active mode. refer to section 6.1, ?dc current characteristics? on page 26 , for i cc values. when the flash device is in active state, it consumes the most power from the system. minimizing flash device active current therefore reduces system power consumption, especially in battery-powered applications. 8.2 automatic power savings (aps) automatic power saving (aps) provides low power operation during a read active state. i ccaps is the average current measured over any 5 ms time interval, 5 s after ce# is deasserted. during aps, average current is measured over the same time interval 5 s after the following events: ? there is no internal read, program or erase activity. ? ce# is asserted. ? the address lines are quiescent, and at v il or v ih . oe# can be driven during aps. 8.3 standby power when ce# is deasserted, the flash device is deselected and placed in standby, substantially reducing power consumption. in standby, the data outputs are placed in high-z, independent of the level placed on oe#. standby current, i ccs , is the average current measured over any 5 ms time interval, 5 s after ce# is deasserted. during standby, average current is measured over the same time interval 5 s after ce# is deasserted. when the flash device is deselected (while ce# is deasserted) during a program or erase operation, it continues to consume active power until the program or erase operation completes. 8.4 power-up/down characteristics the flash device is protected against accidental block erasure or programming during power transitions. power supply sequencing is not required if v cc and v pp are connected together; so it does not matter whether v pp or v cc powers-up first. if v pp is not connected to the system supply, then v cc must attain v ccmin before applying v ccq and v pp . do not drive flash device inputs before supply voltage = v ccqmin. power supply transitions can occur only when rst# is low.
november 2007 datasheet order number: 290702-13 45 numonyx? wireless flash memory (w30) 8.4.1 system reset and rst# the use of rst# during system reset is important with automated program/erase flash devices, because the system expects to read from the flash memory when it comes out of reset. if a cpu reset occurs without a flash memory reset, the cpu is not properly initialized, because the flash memory might be providing status information instead of array data. note: to allow proper cpu/flash device initialization at system reset, connect rst# to the system cpu reset# signal. system designers must guard against spurious writes when vcc voltages are above v lko . because both we# and ce# must be low for a command write, driving either signal to v ih inhibits writes to the flash device. the cui architecture provides additional protection, because memory contents can be altered only after successful completion of the two-step command sequences. the flash device is also disabled until rst# is brought to v ih , regardless of its control input states. by holding the flash device in reset (rst# connected to system powergood) during power-up/down, invalid bus conditions during power-up can be masked, providing yet another level of memory protection. 8.4.2 vcc, vpp, and rst# transitions the cui latches commands issued by system software, and is not altered by vpp or ce# transitions or wsm actions. read-array mode is the power-up default state after the flash device exits from reset mode or after vcc transitions above v lko (lockout voltage). after completing program or block erase operations (even after vpp transitions below v pplk ), the read array command must reset the cui to read-array mode if flash memory array access is desired. 8.5 power supply decoupling when the flash device is accessed, many internal conditions change. circuits are enabled to charge pumps and switch voltages. this internal activity produces transient noise. to minimize the effect of this transient noise, device decoupling capacitors are required. transient current magnitudes depend on the flash device output capacitive and inductive loading. two-line control and proper decoupling capacitor selection suppresses these transient voltage peaks. note: each flash device must have a 0.1 f ceramic capacitor connected between each power (vcc, vccq, vpp) , and ground (vss, vssq) signal. high-frequency, inherently low- inductance capacitors must be as close as possible to the package signals.
numonyx? wireless flash memory (w30) datasheet november 2007 46 order number: 290702-13 numonyx? wireless flash memory (w30) 8.6 reset specifications 8.7 ac i/o test conditions note: input timing begins, and output timing ends, at v ccq /2. input rise and fall times (10% to 90%) < 5 ns. worst case speed conditions are when v cc = v cc min. table 15: reset specifications # symbol parameter 1 notes min max unit p1 t plph rst# low to reset during read 1, 2, 3, 4 100 - ns p2 t plrh rst# low to reset during block erase 1, 3, 4, 5 - 20 s rst# low to reset during program 1, 3, 4, 5 - 10 s p3 t vccph vcc power valid to reset 1,3,4,5,6 60 - s notes: 1. these specifications are valid for all product versions (packages and speeds). 2. the flash device might reset if t plph < t plph min, but this is not guaranteed. 3. not applicable if rst# is tied to vcc. 4. sampled, but not 100% tested. 5. if rst# is tied to vcc, the flash device is not ready until t vccph occurs after when v cc > v cc min. 6. if rst# is tied to any supply/signal with v ccq voltage levels, the rst# input voltage must not exceed v cc until v cc > v cc min. figure 21: reset operations waveforms figure 22: ac input/output reference waveform ( a) reset during read mode (b) reset during program or block erase p1 p2 (c) reset during program or block erase p1 p2 v ih v il v ih v il v ih v il rst# [p] rst# [p] rst# [p] abort complete abort complete v cc 0v vcc (d) vcc power-up to rst# high p1 r5 p2 p3 p2 r5 r5 v ccq 0v v ccq /2 v ccq /2 t e s t p o i n t s input outpu t
november 2007 datasheet order number: 290702-13 47 numonyx? wireless flash memory (w30) note: see ta b l e 1 6 for component values. 8.8 flash device capacitance t a = +25 c, f = 1 mhz figure 23: transient equivalent testing load circuit table 16: test configuration component values for worst case speed conditions test configuration c l (pf) r 1 (k )r 1 (k ) v ccq min standard test 30 25 25 note: c l includes jig capacitance. figure 24: clock input ac waveform device under test v ccq c l r 2 r 1 ou t clk [c] v ih v il r203 r202 r201 symbol parameter typ max unit condition c in input capacitance 6 8 pf v in = 0.0 v c out output capacitance 8 12 pf v out = 0.0 v c ce ce# input capacitance 10 12 pf v in = 0.0 v sampled, not 100% tested.
numonyx? wireless flash memory (w30) datasheet november 2007 48 order number: 290702-13 numonyx? wireless flash memory (w30) 9.0 flash device operations this chapter provides an overview of flash device operations. the w30 flash memory device family includes an on-chip write state machine (wsm) to manage block erase and program algorithms. the wsm command user interface (cui) allows minimal processor overhead with ram-like interface timings. 9.1 bus operations 9.1.1 read the w30 flash memory device has several read configurations: ? asynchronous page mode read. ? synchronous burst mode read ? outputs four , eight, sixteen, or continuous words, from main blocks and parameter blocks. several read modes are available in each partition: ? read-array mode: read accesses return flash memory array data from the addressed locations. ? read identifier mode: reads return manufacturer and device identifier data, block lock status, and protection register data. identifier information can be accessed starting at a 4-mbit partition base addresses; the flash memory array is not accessible in read identifier mode. ? read query mode: reads return the flash device cfi data. cfi information can be accessed starting at a 4-mbit partition base addresses; the flash memory array is not accessible in read query mode. ? read status register mode: reads return status register data from the addressed partition. the array data for that partition is not accessible. a system processor can check the status register to determine the state of an addressed partition, or to monitor program and erase progress. all partitions support the synchronous burst mode that internally sequences addresses with respect to the input clk to select and supply data to the outputs. table 17: bus operations summary bus operation rst# clk adv# ce# oe# we# wait dq[15:0 ] notes read asynchronous v ih xl l l h asserted output - synchronous v ih running l l l h driven output 1 burst suspend v ih halted x l h h active output - write v ih x l l h l asserted input 2 output disable v ih x x l h h asserted high-z 3 standby v ih x x h x x high-z high-z 3 reset v il x x x x x high-z high-z 3,4 notes: 1. wait is valid only during synchronous array-read operations. 2. refer to the table 19, ?bus cycle definitions? on page 52 for valid dq[15:0] during a write operation. 3. x = don?t care (h or l). 4. rst# must be at v ss 0.2 v to meet the maximum specified power-down current.
november 2007 datasheet order number: 290702-13 49 numonyx? wireless flash memory (w30) identifier codes, query data, and status register read operations execute as single- synchronous or asynchronous read cycles . wait is asserted during these reads. access to the modes listed above is independent of v pp . an appropriate cui command places the flash device in a read mode. at initial power-up or after reset, the flash device defaults to asynchronous read-array mode. asserting ce# enables flash device read operations. the flash device internally decodes upper address inputs to determine which partition is accessed. ? asserting adv# opens the internal address latches. ? asserting oe# activates the outputs, and gates the selected data onto the i/o bus. ? in asynchronous mode, the address is latched when adv# is deasserted (when the flash device is configured to use adv#). ? in synchronous mode, the address is latched by either the rising edge of adv# or the rising (or falling) clk edge while adv# remains asserted, whichever occurs first. we# and rst# must be deasserted during read operations. note: if only asynchronous reads are to be performed in your system, clk must be tied to a valid v ih level, the wait signal can be floated, and adv# must be tied to ground. 9.1.2 burst suspend the burst suspend feature allows the system to temporarily suspend a synchronous burst operation if the system needs to use the flash device address and data bus for other purposes. burst accesses can be suspended during the initial latency (before data is received) or after the flash device has output data. when a burst access is suspended, internal array sensing continues and any previously latched internal data is retained. burst suspend occurs when ce# is asserted, the current address has been latched (either adv# rising edge or valid clk edge), clk is halted, and oe# is deasserted. clk can be halted when it is at v ih or v il . to resume the burst access, oe# is reasserted and clk is restarted. subsequent clk edges resume the burst sequence where it left off. within the flash device, ce# gates the wait signal. therefore, during burst suspend, wait remains asserted and does not revert to a high-impedance state when oe# is deasserted. this wait state can cause contention with another flash device attempting to control the system ready signal during a burst suspend. system using the burst suspend feature must not connect the flash device wait signal directly to the system ready signal. refer to figure 15, ?burst suspend? on page 38 . 9.1.3 standby de-asserting ce# deselects the flash device and places it in standby mode, substantially reducing flash device power consumption. in standby mode, outputs are placed in a high-impedance state independent of oe#. if deselected during a program or erase algorithm, the flash device consumes active power until the program or erase operation completes.
numonyx? wireless flash memory (w30) datasheet november 2007 50 order number: 290702-13 numonyx? wireless flash memory (w30) 9.1.4 reset the flash device enters a reset mode when rst# is asserted. in reset mode, internal circuitry is turned off and outputs are placed in a high-impedance state. after returning from reset, a time t phqv is required until outputs are valid, and a delay (t phwv ) is required before a write sequence can be initiated. after this wake-up interval, normal operation is restored. the flash device defaults to read-array mode, the status register is set to 80h, and the read configuration register defaults to asynchronous page-mode reads. if rst# is asserted during an erase or program operation, the operation aborts and the memory contents at the aborted block or address are invalid. see figure 21, ?reset operations waveforms? on page 46 for detailed information regarding reset timings. as on any automated device, rst# must be asserted during system reset. when the system comes out of reset, the processor expects to read from the flash memory array. automated flash memory devices provide status information when read during program or erase operations. if a cpu reset occurs with no flash memory reset, the cpu might not be properly initialized, because the flash memory device might be providing status information instead of array data. 1.8 volt numonyx flash memory devices allow proper cpu initialization following a system reset through the use of the rst# input. in this application, rst# is controlled by the same cpu reset signal, reset#. 9.1.5 write a write occurs when ce# and we# are asserted and oe# is deasserted. flash memory control commands are written to the cui usin g standard microprocessor write timings. proper use of the adv# input is needed for proper latching of the addresses. refer to section 7.3, ?ac write characteristics? on page 38 for details. the address and data are latched on the rising edge of we#. write operations are asynchronous; clk is ignored (but can be kept active/toggling). the cui does not occupy an addressable memory location within any partition. the system processor must access it at the correct address range, depending on the kind of command executed. programming or erasing can occur in only one partition at a time. other partitions must be in one of the read modes or erase suspend mode. table 18, ?command codes and descriptions? on page 51 shows the available commands. appendix a, ?write state machine? on page 86 provides information about moving between different operating modes using cui commands. 9.2 flash device commands the flash device on-chip wsm manages erase and program algorithms. this local cpu (wsm) controls the flash device in-system read, program, and erase operations. bus cycles to or from the flash memory device conform to standard microprocessor bus cycles. the rst#, ce#, oe#, we#, and adv# control signals dictate data flow into and out of the flash device. wait informs the cpu of valid data during burst reads. table 17, ?bus operations summary? on page 48 summarizes bus operations. to select flash device operations, write specific commands into the flash device cui. table 18, ?command codes and descriptions? on page 51 lists all possible command codes and descriptions. table 19, ?bus cycle definitions? on page 52 lists command definitions. because commands are partitio n-specific, you must issue write commands within the target address range.
november 2007 datasheet order number: 290702-13 51 numonyx? wireless flash memory (w30) table 18: command codes and descriptions (sheet 1 of 2) operation code flash device command description read ffh read array places the selected partition in read-array mode. 70h read status register places the selected partition in status register read mode. the partition enters this mode after a program or erase command is issued to it. 90h read identifier places the selected partition in read identifier mode. flash device reads from partition addresses output the manufacturer/device codes, configuration register data, block lock status, or protection register data on d[15:0]. 98h read query places the addressed partition in read query mode. flash device reads from the partition addresses output the cfi information on d[7:0]. 50h clear status register the wsm can set the block lock (sr[1]), v pp (sr[3]), program (sr[4]), and erase (sr[5]) status bits of the status register, but wsm cannot clear these bits. sr[5:3,1] can be cleared only by a flash device reset or through the clear status register command. program 40h word program setup ? the first cycle of this preferred program command prepares the cui for a program operation. ? the second cycle latches the address and data, and executes the wsm program algorithm at this location. status register updates occur when ce# or oe# is toggled. after programming, use a read array command to read the array data. 10h alternate setup equivalent to a program setup command (40h). 30h efp setup this program command activates efp mode. ? the first write cycle sets up the command. ? if the second cycle is an efp confirm command (d0h), subsequent writes provide program data. all other commands are ignored after efp mode begins. d0h efp confirm if the first command was efp setup (30h), the cui latches the address and data, and prepares the flash device for efp mode. erase 20h erase setup this command prepares the cui for block erase. the flash device erases the block that the erase confirm command addresses. if the next command is not erase confirm, the cui sets status register bits sr[5:4] to indicate a command sequence error, and places the partition in the read status register mode. d0h erase confirm if the first command was erase setup (20h), the cui latches the address and data, and erases the block indicated by the erase confirm cycle address. during program or erase, the partition responds only to read status register, program suspend, and erase suspend commands. ce# or oe# toggle updates the status register data. suspend b0h program suspend or erase suspend this command, issued at any flash device address, suspends the currently executing program or erase operation. status register data indicates that the operation was successfully suspended if sr[2] (program suspend) or sr[6] (erase suspend) and sr[7] are set. the wsm remains in the suspended state regardless of the control signal states (except rst#). d0h suspend resume this command, issued at any flash device address, resumes the suspended program or erase operation. block locking 60h lock setup this command prepares the cui lock configuration. if the next command is not lock block, unlock block, or lock-down, the cui sets sr[5:4] to indicate a command sequence error. 01h lock block if the previous command was lock setup (60h), the cui locks the addressed block. d0h unlock block if the previous command was lock setup (60h), the cui latches the address and unlocks the addressed block. if previously locked-down, the operation has no effect. 2fh lock-down if the previous command was lock setup (60h), the cui latches the address and locks-down the addressed block.
numonyx? wireless flash memory (w30) datasheet november 2007 52 order number: 290702-13 numonyx? wireless flash memory (w30) protection c0h protection program setup this command prepares the cui for a protection register program operation. the second cycle latches address and data, and starts the wsm protection register program or lock algorithm. toggling ce# or oe# updates the flash device status register data. to read array data after programming, issue a read array command. configuration 60h configuration setup this command prepares the cui for flash device configuration. if set configuration register is not the next command, the cui sets sr[5:4] to indicate a command sequence error. 03h set configuration register if the previous command was configuration setup (60h), the cui latches the address and writes the data from a[15:0] into the configuration register. subsequent read operations access the array data. note: do not use unassigned commands. numonyx reserves the right to redefine these codes for future functions. table 19: bus cycle definitions operation command bus cycles first bus cycle second bus cycle oper addr 1 data 2,3 oper addr 1 data 2,3 read read array/reset > 1 write pna ffh read read address array data read identifier > 2 write pna 90h read pba+ia ic read query > 2 write pna 98h read pba+qa qd read status register 2 write pna 70h read pna srd clear status register 1 write xx 50h program and erase block erase 2 write ba 20h write ba d0h word program 2 write wa 40h/10h write wa wd efp > 2 write wa 30h write wa d0h program/erase suspend 1 write xx b0h program/erase resume 1 write xx d0h lock lock block 2 write ba 60h write ba 01h unlock block 2 write ba 60h write ba d0h lock-down block 2 write ba 60h write ba 2fh table 18: command codes and descriptions (sheet 2 of 2) operation code flash device command description
november 2007 datasheet order number: 290702-13 53 numonyx? wireless flash memory (w30) 9.3 command sequencing when issuing a 2-cycle write sequence to the flash device, a read operation can occur between the two write cycles. the setup phase of a 2-cycle write sequence places the addressed partition into read-status mode, so if the same partition is read before the second confirm write cycle is issued, status register data is returned. reads from other partitions, however, can return actual array data, if the addressed partition is already in read-array mode. figure 25 and figure 26 illustrate these two conditions. protection protection program 2 write pa c0h write pa pd lock protection program 2 write lpa c0h write lpa fffdh configuration set configuration register 2 write cd 60h write cd 03h notes: 1. first-cycle command addresses must be the same as the target address of the operation. examples: ?the first-cycle address for the read identifier command must be the same as the identification code address (ia). ?the first-cycle address for the word program command must be the same as the word address (wa) to be programmed. ?the first-cycle address for the erase/program suspend command must be the same as the address within the block to be suspended. xx= any valid address within the flash device. ia= identification code address. ba= block address. any address within a specific block. lpa= the lock protection address is obtained from the cfi (through the read query command). the w30 flash memory device family lpa is at 0080h. pa= user programmable 4-word protection address. pna= any address within a specific partition. pba= partition base address. the first address of a particular partition. qa= query code address. wa= word address of memory location to be written. 2. srd= status register data. wd= data to be written at location wa. ic= identifier code data. pd= user programmable 4-word protection data. qd= query code data on d[7:0]. cd= configuration register code data presented on flash device addresses a[15:0]. a[max:16] address bits can select any partition . see table 27, ?read configuration register definitions? on page 79 for configuration register bits descriptions. 3. do not use commands other than those shown above. other commands are reserved by numonyx for future flash device implementations. table 19: bus cycle definitions operation command bus cycles first bus cycle second bus cycle oper addr 1 data 2,3 oper addr 1 data 2,3 figure 25: normal write and read cycles partition a partition a partition a 20h d0h ffh block erase setup block erase conf irm read array a ddress [a] we# [w] oe# [g] data [q]
numonyx? wireless flash memory (w30) datasheet november 2007 54 order number: 290702-13 numonyx? wireless flash memory (w30) by contrast, a write bus cycle must not interrupt a 2-cycle write sequence. such an interruption causes a command sequence error to appear in the status register. figure 27 illustrates a command sequence error. figure 26: interleaving a 2-cycle write sequence with an array read partition b partition a partition b partition a ffh 20h a rray dat a d0h read array erase setup bus read erase conf irm a ddress [a] we# [w] oe# [g] data [q] figure 27: improper command sequencing partition x partition y partition x partition x 20 h ffh d0h sr data a ddress [a] we# [w] oe# [g] data [d/q]
november 2007 datasheet order number: 290702-13 55 numonyx? wireless flash memory (w30) 10.0 read operations 10.1 read array the read array command places (or resets) the partition in read-array mode and is used to read data from the flash memory array. upon initial flash device power-up, or after reset (rst# transitions from v il to v ih ), all partitions default to asynchronous read-array mode. to read array data from the flash device: 1. write the read array command (ffh) to the cui and specify the desired word address. 1. read from that address. note: if a partition is already in read-array mode, you do not need to issue the read array command to read from that partition. if the read array command is written to a partition that is erasing or programming, the flash device presents invalid data on the bus until the program or erase operation completes. after the program or erase finishes in that partition, valid array data can then be read. if an erase suspend or program suspend command suspends the wsm, a subsequent read array command places the addressed partition in read-array mode. the read array command functions independently of v pp . 10.2 read device id the read identifier mode outputs the manufacturer/device identifier, block lock status, protection register codes, and configuration register data. the identifier information is contained within a separate memory space on the flash device, and can be accessed along the 4-mbit partition address range supplied by the read identifier command (90h) address. reads from addresses in ta b l e 2 0 retrieve id information. issuing a read identifier command to a partition that is programming or erasing places the outputs of that partition in read id mode while the partition continues to program or erase in the background. table 20: flash device identification codes (sheet 1 of 2) item address 1 data description base offset manufacturer id partition 00h 0089h numonyx device id partition 01h 8852h 32-mbit tpd 8853h 32-mbit bpd 8854h 64-mbit tpd 8855h 64-mbit bpd 8856h 128-mbit tpd 8857h 128-mbit bpd block lock status ( 2 ) block 02h d0 = 0 block is unlocked d0 = 1 block is locked
numonyx? wireless flash memory (w30) datasheet november 2007 56 order number: 290702-13 numonyx? wireless flash memory (w30) 10.3 read query (cfi) the w30 flash memory device contains a separate cfi query database that acts as an on-chip datasheet. to access the cfi information within the w30 flash memory device, issue the read query command and supply a specific address. the address is constructed from the base address of a partition plus a particular offset corresponding to the desired cfi field. appendix b, ?common flash interface? on page 89 shows accessible cfi fields and their address offsets. issuing the read query command to a partition that is programming or erasing puts that partition in read query mode while the partition continues to program or erase in the background. 10.4 read status register the flash device status register displays program and erase operation status. the status of a partition can be read after writing the read status register command to any location within the address range of that partition. read-status mode is the default read mode following a program, erase, or lock block command sequence. subsequent single reads from that partition return the partition status until another valid command is written. the read-status mode supports single synchronous and single asynchronous reads only; it does not support burst reads. the first falling edge of oe# or ce# latches and updates status register data. the operation does not affect the modes of other partitions. because the status register is 8 bits wide, only dq [7:0] contain valid status register data; dq [15:8] contain zeros. see table 21, ?status register definitions? on page 57 and table 22, ?status register descriptions? on page 57 . each 4-mbit partition contains its own status register. bits sr[6:0] are unique to each partition, but sr[7], the device wsm status (dws) bit, pertains to the entire flash memory device. sr[7] provides the program and erase status of the entire flash device. by contrast, the partition wsm status (pws) bit, sr[0], provides program and erase status of the addressed partition only. status register bits sr[6:1] present information about partition-specific program, erase, suspend, v pp , and block-lock states. table 23, ?status register device wsm and partition write status description? on page 57 describes the dws (sr[7]) and pws (sr[0]) combinations. block lock-down status ( 2 ) block 02h d1 = 0 block is not locked-down d1 = 1 block is locked down configuration register partition 05h register data protection register lock status partition 80h lock data protection register partition 81h - 88h register data multiple reads required to read the entire 128-bit protection register. notes: 1. the address is constructed from a base address plus an offset. for example, to read the block lock status for block number 38 in a bpd, set the address to the bba (0f8000h) plus the offset (02h), which in this example is 0f8002h. then examine bit 0 of the data to determine whether the block is locked. 2. see section 13.1.4, ?block lock status? on page 73 for valid lock status. table 20: flash device identification codes (sheet 2 of 2) item address 1 data description base offset
november 2007 datasheet order number: 290702-13 57 numonyx? wireless flash memory (w30) table 21: status register definitions dws ess es ps vpps pss dps pws 76543210 table 22: status register descriptions bit name state description 7 dws device wsm status 0 = device wsm is busy 1 = device wsm is ready ? sr[7] indicates erase or program completion in the flash device. ? sr[6:1] are invalid while sr[7] = 0. see ta b l e 2 3 for valid sr[7] and sr[0] combinations. 6 ess erase suspend status 0 = erase in progress/completed 1 = erase suspended after issuing an erase suspend command, the wsm halts and sets sr[7] and sr[6]. sr[6] remains set until the flash device receives an erase resume command. 5 es erase status 0 = erase successful 1 = erase error ? sr[5] is set if an attempted erase failed. ? a command sequence error is indicated when sr[7,5:4] are set. 4 ps program status 0 = program successful 1 = program error sr[4] is set if the wsm failed to program a word. 3 vpps vpp status 0 = v pp ok 1 = v pp low detect, operation aborted the wsm indicates the v pp level after program or erase completes. sr[3] does not provide continuous v pp feedback and is not guaranteed when v pp v ppl /v pph 2 pss program suspend status 0 = program in progress/completed 1 = program suspended after receiving a program suspend command, the wsm halts execution and sets sr[7] and sr[2]. these bits remain set until a resume command is received. 1 dps device protect status 0 = unlocked 1 = aborted erase/program attempt on a locked block if an erase or program operation is attempted to a locked block (if wp# = v il ), the wsm sets sr[1] and aborts the operation. 0 pws partition write status 0 = this partition is busy, but only if sr[7]=0 1 = another partition is busy, but only if sr[7]=0 the addressed partition is erasing or programming. in efp mode, sr[0] indicates that a data-stream word has finished programming or verifying, depending on the particular efp phase. see ta b l e 2 3 for valid sr[7] and sr[0] combinations. table 23: status register device wsm and partition write status description dws (sr[7]) pws (sr[0]) description 00 the addressed partition is performing a program/erase operation. efp: the flash device has finished programming or verifying data, or is ready for data. 01 a partition other than the one currently addressed is performing a program/erase operation. efp: the flash device is either programming or verifying data. 10 no program/erase operation is in progress in any partition. erase and program suspend bits (sr[6,2]) indicate whether other partitions are suspended. efp: the flash device has exited efp mode. 11 does not occur in standard program or erase modes. efp: this combination does not occur.
numonyx? wireless flash memory (w30) datasheet november 2007 58 order number: 290702-13 numonyx? wireless flash memory (w30) 10.5 clear status register the clear status register command clears the status register and leaves all partition output states unchanged. the wsm can set all status register bits and clear bits sr[7:6,2,0]. because bits sr[5,4,3,1] indicate various error conditions, they can be cleared only by the clear status register command. by allowing system software to reset these bits, several operations (such as cumulatively programming several addresses or erasing multiple blocks in sequence) can be performed before reading the status register to determine whether an error occurred. if an error is detected, the status register must be cleared before beginning another command or sequence. flash device reset (rst# = v il ) also clears the status register. this command functions independently of v pp .
november 2007 datasheet order number: 290702-13 59 numonyx? wireless flash memory (w30) 11.0 program operations 11.1 word program when the word program command is issued, the wsm executes a sequence of internally timed events to program a word at the desired address, and to verify that the bits are sufficiently programmed. programming the flash memory array changes specifically addressed bits to 0; 1 bits do not change the memory cell contents. programming can occur in only one partition at a time. all other partitions must be in either a read mode or erase suspend mode. only one partition can be in erase suspend mode at a time. to examine the status register can be examined for program progress, read any address within the partition that is busy programming. however, while most status register bits are partition-specific, the device wsm status bit, sr[7], is device -specific. that is, if the status register is read from any other partition, sr[7] indicates the program status of the entire flash memory device. this status bit permits the system cpu to monitor the program progress while reading the status of other partitions. ce# or oe# toggle (during polling) updates the status register. several commands can be issued to a partition that is programming: read status register, program suspend, read identifier, and read query. the read array command can also be issued, but the read data is indeterminate. after programming completes, three status register bits can signify various possible error conditions: ? sr[4] indicates a program failure if set. ? if sr[3] is set, the wsm could not execute the word program command, because v pp was outside the acceptable limits. ? if sr[1] is set, the program was aborted, because the wsm attempted to program a locked block. after the status register data is examined, clear it using the clear status register command before issuing a new command. the partition remains in status register mode until another command is written to that partition. any command can be issued after the status register indicates program completion. if ce# is deasserted while the flash device is programming, the flash devices do not enter standby mode until the program operation completes.
numonyx? wireless flash memory (w30) datasheet november 2007 60 order number: 290702-13 numonyx? wireless flash memory (w30) 11.2 factory programming the standard factory programming mode uses the same commands and algorithm as the word program mode (40h/10h). when v pp is at v ppl , program and erase currents are drawn through vcc. if vpp is driven by a logic signal, v ppl must remain above the v ppl min value to perform in-system flash memory modifications. when vpp is connected to a 12 v power supply, the flash device draws program and erase current directly from vpp, which eliminates the need for an external switching transistor to control the v pp voltage. figure 28: word program flowchart suspend program loop start write 40h, word address write data word address read status register sr[7] = full program status check (if desired) program complete full program status check procedure suspend program read status register program successful sr[3] = sr[1] = 0 0 sr[4] = 0 1 1 1 1 0 no yes v pp range error device protect error program error word program procedure sr[3] must be cleared before the wsm will allow further program attempts only the clear staus register command clears sr[4:3,1]. if an error is detected, clear the status register before attempting a program retry or other error recovery. standby standby bus operation command check sr[3] 1 = v pp error check sr[4] 1 = data program error comments repeat for subsequent programming operations. full status register check can be done after each program or after a sequence of program operations. comments bus operation command data = 40h addr = location to program (wa) write program setup data = data to program (wd) addr = location to program (wa) write data read srd toggle ce# or oe# to update srd read check sr[7] 1 = wsm ready 0 = wsm busy standby standby check sr[1] 1 = attempted program to locked block program aborted
november 2007 datasheet order number: 290702-13 61 numonyx? wireless flash memory (w30) figure 37, ?examples of vpp power supply configurations? on page 78 shows examples of flash device power supply usage in various configurations. the 12-v v pp mode enhances programming performance during the short time period typically found in manufacturing processes. however, this mode is not intended for extended use.12 v can be applied to v pp during program and erase operations as specified in section 5.2, ?operating conditions? on page 24 . vpp can be connected to 12 v for a total of t pph hours maximum. stressing the flash device beyond these limits might cause permanent damage. 11.3 enhanced factory program (efp) efp substantially improves flash device programming performance through a number of enhancements to the conventional 12-volt word program algorithm. the more efficient wsm algorithm in efp eliminates the traditional overhead delays of the conventional word program mode in both the host programming system and the flash device. changes to the conventional word programming flowchart and internal wsm routine were developed because of today's beat-rate-sensitive manufacturing environments; a balance between programming speed and cycling performance was attained. the host programmer writes data to the flash device and checks the status register to determine when the data has completed programming. this modification cuts write bus cycles approximately in half. ? following each internal program pulse, the wsm increments the flash device address to the next physical location. ? programming equipment can then sequentially stream program data throughout an entire block without having to setup and present each new address. in combination, these enhancements reduce much of the host programmer overhead, enabling more of a data streaming approach to flash device programming. efp further speeds up programming by performing internal code verification. with this feature, prom programmers can rely on the flash device to verify that it has been programmed properly. from the flash device side, efp streamlines internal overhead by eliminating the delays previously associated with switching voltages between programming and verify levels at each memory-word location. efp consists of four phases: setup, program, verify, and exit. refer to figure 29, ?enhanced factory program flowchart? on page 64 for a detailed graphical representation of how to implement efp. 11.3.1 efp requirements and considerations table 24: efp requirements and considerations efp requirements efp considerations ambient temperature: t a = 25 c 5 c block cycling below 100 erase cycles 1 v cc within specified operating range rww not supported 2 v pp within specified v pph range efp programs one block at a time target block unlocked efp cannot be suspended 1. recommended for optimum performance. some degradation in performance might occur if this limit is exceeded, but the internal algorithm will continue to work properly. 2. code or data cannot be read from another partition during efp.
numonyx? wireless flash memory (w30) datasheet november 2007 62 order number: 290702-13 numonyx? wireless flash memory (w30) 11.3.2 setup after receiving the efp setup (30h) and efp confirm (d0h) command sequence, sr[7] transitions from a 1 to a 0, indicating that the wsm is busy with efp algorithm startup. a delay before checking sr[7] is required to allow the wsm time to perform all of its setups and checks (v pp level and block lock status). if an error is detected, status register bits sr[4], sr[3], and/or sr[1] are set, and the efp operation terminates. note: after the efp setup and confirm command sequence, reads from the flash device automatically output status register data. do not issue the read status register command, because this command is interpreted as data to program at wa 0 . 11.3.3 program after setup completion, the host programming system must check sr[0] to determine the data-stream ready status (sr[0]=0). each subsequent write after this check is a program-data write to the flash memory array. each cell within the memory word to be programmed to 0 receives one wsm pulse; additional pulses, if required, occur in the verify phase. sr[0]=1 indicates that the wsm is busy applying the program pulse. the host programmer must poll the flash device status register for the program done state after each data-stream write. sr[0]=0 indicates that the appropriate cell(s) within the accessed memory location have received their single wsm program pulse, and that the flash device is ready for the next word. although the host can check full status for errors at any time, this check is necessary only on a block basis, after efp exit. addresses must remain within the target block. supplying an address outside of the target block immediately terminates the program phase; the wsm then enters the efp verify phase. the address can either remain constant or increment. the flash device compares the incoming address to the address stored from the setup phase (wa 0 ). ? if the addresses match, the wsm programs the new data word at the next sequential memory location. ? if the addresses differ, the wsm jumps to the new address location. the program phase concludes when the host programming system writes to a different block address. the data supplied must be ffffh. upon program phase completion, the flash device enters the efp verify phase. 11.3.4 verify a high percentage of the flash memory bits program on the first wsm pulse. however, efp internal verification identifies cells that do not completely program on their first attempt, and applies additional pulses as required. the verify phase is identical in flow to the program phase, except that instead of programming incoming data, the wsm compares the verify-stream data to the data that was previously programmed into the block. ? if the data compares correctly, the host programmer proceeds to the next word. ? if the data does not match, the host waits while the wsm applies one or more additional pulses.
november 2007 datasheet order number: 290702-13 63 numonyx? wireless flash memory (w30) the host programmer must reset its initial verify-word address to the same starting location supplied during the program phase. it then reissues each data word in the same order as during the program phase. like programming, the host can write each subsequent data word to wa 0 or it can increment through the block addresses. the verification phase concludes when the interfacing programmer writes to a different block address. the data supplied must be ffffh. upon completion of the verify phase, the flash device enters the efp exit phase. 11.3.5 exit sr[7]=1 indicates that the flash device has returned to normal operating conditions. perform a full status check at this time, to verify that the entire block programmed successfully. after efp exit, any valid cui command can be issued.
numonyx? wireless flash memory (w30) datasheet november 2007 64 order number: 290702-13 numonyx? wireless flash memory (w30) figure 29: enhanced factory program flowchart efp setup efp program efp verify efp exit 1. wa 0 = first word address to be programmed within the target block. the bba (block base address) must remain constant throughout the program phase data stream; wa can be held constant at the first address location, or it can be written to sequence up through the addresses within the block. writing to a bba not equal to that of the block currently being written to terminates the efp program phase, and instructs the device to enter the efp verify phase. 2. for proper verification to occur , the verify data stream must be presented to the device in the same sequence as that of the program phase data stream. writing to a bba not equal to wa terminates the efp verify phase, and instructs the device to exit efp . 3. bits that did not fully program with the single wsm pulse of the efp program phase receive additional program-pulse attempts during the efp verify phase. the device will report any program failure by setting sr[4]=1; this check can be performed during the full status check after efp has been exited for that block, and will indicate any error within the entire data stream. comments bus state repeat for subsequent operations. after efp exit, a full status check can determine if any program error occurred. see the full status check procedure in the word program flowchart. write standby read write write (note 2) read standby write read standby efp setup program done? exit program phase last data? exit verify phase efp exited? write efp confirm read standby efp setup done? read standby verify stream ready? write unlock block write (note 1) standby last data? standby (note 3) verify done? sr [0]= 1=n write data address = wa 0 last data? write ffffh address bba program done? read status register sr[0]=0=y y sr [0]= 1=n n write data address = wa 0 verify done? last data? read status register write ffffh address bba y verify stream ready? read status register sr[7]=0=n full status check procedure operation complete read status register efp exited? sr[7]=1=y sr[0 ]=1=n start write 30h address = wa 0 v pp = 12v unlock block write d0h address = wa 0 efp setup done? read status register sr[7]=1=n exit n efp program efp verify efp exit efp setup enhanced factory programming procedure comments bus state data = 30h address = wa 0 data = d0h address = wa 0 status register check sr[7] 0 = efp ready 1 = efp not ready v pp = 12v unlock block check sr[0] 0 = program done 1 = program not done status register data = ffffh addressnot within same bba data = data to program address = wa 0 device automatically increments address. comments bus state data = word to ve rify address = wa 0 status register device automatically increments address. data = ffffh address not within same bba status register check sr[0] 0 = ready for verify 1 = not ready for verify check sr[0] 0 = verify done 1 = verify not done status register check sr[7] 0 = exit not finished 1 = exit completed check v pp & lock errors (sr[3,1]) data stream ready? read status register sr[0 ] =0=y sr [7]=0=y sr[0 ]=1=n standby read data stream ready? check sr[0] 0 = ready for data 1 = not ready for data status register sr[0]=0=y sr[0] =0=y efp setup time standby efp setup time standby error condition check if sr[7] = 1: check sr[3,1] sr[3 ] = 1 = v pp error sr[1 ] = 1 = locked block
november 2007 datasheet order number: 290702-13 65 numonyx? wireless flash memory (w30) 12.0 program and erase operations 12.1 program/erase suspend and resume the program suspend and erase suspend commands halt an in - progress program or erase operation. the command can be issued at any flash device address. the partition corresponding to the address of the command remains in its previous state. a suspend command allows data to be accessed from memory locations other than the location being programmed or the block being erased. ? a program operation can be suspended only to perform a read operation. ? an erase operation can be suspended to perform either a program or a read operation within any block, except the block that is erase suspended. ? a program command nested within a suspended erase can subsequently be suspended to read yet another location. once a program or erase process starts, the suspend command requests that the wsm suspends the program or erase sequence at predetermined points in the algorithm. the partition that is actually suspended continues to output status register data after the suspend command is written. an operation is suspended when status bits sr[7] and sr[6] and/or sr[2] are set. to read data from blocks within the partition (other than an erase-suspended block), write a read array command. block erase cannot resume until the program operations initiated during erase suspend are complete. ? read array, read status register, read identifier (id), read query, and program resume are valid commands during program or erase suspend. ? additionally, clear status register, program, program suspend, erase resume, lock block, unlock block, and lock-down block are valid commands during erase suspend. to read data from a block in a partition that is not programming or erasing, the operation does not need to be suspended. ? if the other partition is already in read array, id, or query mode, issuing a valid address returns corresponding data. ? if the other partition is not in a read mode, one of the read commands must be issued to the partition before data can be read. during a suspend, ce# = v ih places the flash device in standby state, which reduces active current. v pp must remain at its program level and wp# must remain unchanged while in suspend mode. a resume command instructs the wsm to continue programming or erasing, and clears status register bits sr[2] (or sr[6]) and sr[7]. the resume command can be written to any partition. when read at the partition that is programming or erasing, the flash device outputs data corresponding to the last mode for that partition. if the status register error bits are set, the status register can be cleared before issuing the next instruction. rst# must remain at v ih . see figure 30, ?program suspend / resume flowchart? on page 66 , and figure 31, ?erase suspend / resume flowchart? on page 67 . if a suspended partition was placed in read array, read status register, read identifier (id), or read query during the suspend, the flash device remains in that mode, and outputs data corresponding to that mode after the program or erase operation resumes.
numonyx? wireless flash memory (w30) datasheet november 2007 66 order number: 290702-13 numonyx? wireless flash memory (w30) after resuming a suspended operation, issue the read command appropriate to the read operation. to read status after resuming a suspended operation, issue a read status register command (70h) to return the suspended partition to status mode. figure 30: program suspend / resume flowchart read status register sr[7] = sr[2] = write ffh susp partition read array data program completed done reading write ffh pgm'd partition write d0h any address program resumed read array data 0 no 0 yes 1 1 program suspend / resume procedure write program resume data = d0h addr = any device address bus operation command comments write program suspend data = b0h addr = any address within programming partition standby check sr[7] 1 = wsm ready 0 = wsm busy standby check sr[2] 1 = program suspended 0 = program completed write read array data = ffh addr = any device address (except word being programmed) read read array data from block other than the one being programmed read read srd toggle ce# or oe# to update srd addr = any address in same partition start write b0h any address write 70h same partition write read status data = 70h addr = any address in same partition if the suspended partition was placed in read array mode: write read status return partition to status mode: data = 70h addr = address within same partition write 70h same partition
november 2007 datasheet order number: 290702-13 67 numonyx? wireless flash memory (w30) 12.2 block erase the 2-cycle block erase command sequence, consisting of erase setup (20h) and erase confirm (d0h), initiates one block erase at the addressed block. only one partition can be in an erase mode at a time; other partitions must be in a read mode. the erase confirm command internally latches the address of the block to erase. erase forces all bits within the block to 1. sr[7] is cleared while the erase executes. after writing the erase confirm command, the selected partition is placed in read status register mode. reads performed to that partition return the current status data. the address given during the erase confirm command does not need to be the same figure 31: erase suspend / resume flowchart erase completed write ffh erased partition read array data 0 0 no read 1 program program loop read array data 1 yes start write b0h any address read status register sr[7] = sr[6] = write d0h any address erase resumed read or program? done? write write standby standby write erase suspend read array or program erase resume data = b0h addr = any address data = ffh or 40h addr = any device address (except block being erased) check sr[7] 1 = wsm ready 0 = wsm busy check sr[6] 1 = erase suspended 0 = erase completed data = d0h addr = any address bus operation command comments read read srd toggle ce# or oe# to update srd addr = any address in same partition read or write read array or program data from/to block other than the one being erased erase suspend / resume procedure write 70h same partition write read status data = 70h addr = any address in same partition write 70h same partition if the suspended partition was placed in read array mode or a program loop: write read status return partition to status mode: data = 70h addr = address within same partition
numonyx? wireless flash memory (w30) datasheet november 2007 68 order number: 290702-13 numonyx? wireless flash memory (w30) address used in the erase setup command. for example, if the erase confirm command is given to partition b, then the selected block in partition b is erased, even if the erase setup command was to partition a. the 2-cycle erase sequence cannot be interrupted with a bus write operation. for example, to execute properly, an erase setup command must be immediately followed by the erase confirm command. if a different command is issued between the setup and confirm commands, the following occurs: ? the partition is placed in read-status mode. ? the status register signals a command sequence error. ? all subsequent erase commands to that partition are ignored until the status register is cleared. to detect block erase completion, the cpu analyzes sr[7] of that partition. if an error bit (sr[5,3,1]) was flagged, the status register can be cleared by issuing the clear status register command before attempting the next operation. the partition remains in read-status mode until another command is written to its cui. any cui instruction can follow after erasing completes. the cui can be set to read-array mode to prevent inadvertent status register reads.
november 2007 datasheet order number: 290702-13 69 numonyx? wireless flash memory (w30) 12.3 read-while-write and read-while-erase the product name supports flexible multi-partition dual-operation architecture. by dividing the flash memory into many separate partitions, the flash device can read from one partition while programing (read-while-write) or erasing (read-while-eras) in another partition. both of these features greatly enhance data storage performance. the w30 flash memory device does not support simultaneous program and erase operations. attempting to perform operations such as these results in a command sequence error. only one partition can be programming or erasing while another figure 32: block erase flowchart sr[3,1] must be cleared before the wsm will allow further erase attempts. only the clear status register command clears sr[5:3,1]. if an error is detected, clear the status register before attempting an erase retry or other error recovery. start full erase status check procedure repeat for subsequent block erasures. full status register check can be done after each block erase or after a sequence of block erasures. no suspend erase 1 0 0 0 1 1 1 1 0 yes suspend erase loop 0 write 20h block address write d0h and block address read status register sr[7] = full erase status check (if desired) block erase complete read status register block erase successful sr[1] = erase of locked block aborted block erase procedure bus operation command comments write block erase setup data = 20h addr = block to be erased (ba) write erase confirm data = d0h addr = block to be erased (ba) read read srd toggle ce# or oe# to update srd standby check sr[7] 1 = wsm ready 0 = wsm busy bus operation command comments sr[3] = v pp range error sr[5:4] = command sequence error sr[5] = block erase error standby check sr[3] 1 = v pp error standby check sr[5:4] both 1 = command sequence error standby check sr[5] 1 = block erase error standby check sr[1] 1 = attempted erase of locked block erase aborted
numonyx? wireless flash memory (w30) datasheet november 2007 70 order number: 290702-13 numonyx? wireless flash memory (w30) partition is reading. however, one partition can be in erase suspend mode while a second partition is performing a program operation, and yet another partition is executing a read command. table 18, ?command codes and descriptions? on page 51 describes the command codes available for all functions.
november 2007 datasheet order number: 290702-13 71 numonyx? wireless flash memory (w30) 13.0 security modes the w30 flash memory device offers both hardware and software security features to protect the flash memory data. ? to use the software security feature, execute the lock block command. ? to use the hardware security feature, execute the lock-down block command and assert the wp# signal. refer to figure 33, ?block locking state diagram? on page 72 for a state diagram of the flash device security features. also see figure 34, ?locking operations flowchart? on page 75 . 13.1 block lock operations individual instant block locking protects code and data by allowing any block to be locked or unlocked with no latency. this locking scheme offers two levels of protection: ? software-only control of block locking (useful for frequently changed data blocks). ? hardware interaction before locking can be changed (protects infrequently changed code blocks). the following sections discuss the locking system operation. the term state [abc] specifies locking states, such as state [001]. in this syntax: ?a= wp# value. ? b = block lock-down status bit d1. ? c = block lock status register bit d0. figure 33, ?block locking state diagram? on page 72 defines possible locking states. the following summarizes the locking functionality. ? all blocks power-up in a locked state. ? unlock commands can unlock these blocks, and lock commands can lock them again. ? the lock-down command locks a block and prevents it from being unlocked when wp# is asserted. ? locked-down blocks can be unlocked or locked with commands as long as wp# is deasserted. ? when wp# is asserted, previously locked-down blocks return to lock-down. ? the lock-down status bit clears only when the flash device is reset or powered- down. block lock registers are not affected by the v pp level. these registers can be modified and read even if v pp < v pplk . the locking status of each block can be se t to locked, unlocked, and lock-down, as described in the following sections. see figure 34, ?locking operations flowchart? on page 75 .
numonyx? wireless flash memory (w30) datasheet november 2007 72 order number: 290702-13 numonyx? wireless flash memory (w30) 13.1.1 lock all blocks default to locked (state [x01]) after initial power-up or reset. locked blocks are fully protected from alteration. attempted program or erase operations to a locked block return an error in sr[1]. ? to lock unlocked blocks, use the lock block command sequence. ? to change the status of a locked block to unlocked or lock-down, use the appropriate software commands. 13.1.2 unlock unlocked blocks (states [x00] and [110]) can be programmed or erased. all unlocked blocks return to the locked state when the flash device is reset or powered-down. ? to change the status of an unlocked block to the locked or locked-down state, use the appropriate software commands. ? to unlock a locked block, write the unlock block command sequence if the block is not locked-down. 13.1.3 lock-down locked-down blocks (state [011]) offer an additional level of write protection beyond the protection of a regular locked block. if a block is locked-down, the software cannot change the state of the block if wp# is asserted. figure 33: block locking state diagram notes: 1. [a,b,c] represents [wp#, d1, d0]. x = don?t care. 2. d1 indicates block lock -down status. - d1 = 0, lock -down has not been issued to this block . - d1 = 1, lock -down has been issued to this block . 3. d0 indicates block lock status. - d0 = 0, block is unlocked. - d0 = 1, block is locked. 4. locked-down = hardware + software locked. 5. [011 ] states should be tracked by system software to determine difference between hardware locked and locked -down states. software block lock (0x60/0x01) or software block unlock (0x60/0xd0) software block lock-down (0x60/0x2f) wp# hardware control [x00] power -up/reset unlocked [111] [110 ] software locked [011] hardware locked 5 unlocked wp# hardware control [x 01 ] locked [011] locked - down 4,5 b5070
november 2007 datasheet order number: 290702-13 73 numonyx? wireless flash memory (w30) ? to lock-down a locked or unlocked block, write the lock-down block command sequence. ? if a block was set to locked-down, then later changed to unlocked, issue the lock- down command before asserting wp#, to put that block back in the locked-down state. ? when wp# is deasserted, locked-down blocks change to the locked state, and can then be unlocked using the unlock block command. 13.1.4 block lock status the lock status of every block can be read in read identifier mode. note: to enter this mode, issue the read identifier command to the flash device. subsequent reads at bba + 02h output the lock status of that block. for example, to read the block lock status of block 10, the address sent to the flash device must be 50002h (for a top-parameter device). the lowest two data bits of the read data, dq1 and dq0, represent the lock status. ? dq0 indicates the block lock status. this bit is set using the lock block command and cleared using the block unlock command. it is also set when entering the lock- down state. ? dq1 indicates lock-down status and is set using the lock-down command. the lock-down status bit cannot be cleared by software?only by a flash device reset or power-down. see ta b l e 2 5 . 13.1.5 lock during erase suspend block lock configurations can be performed during an erase suspend operation, using the standard locking command sequences to unlock, lock, or lock-down a block. this feature is useful when another block requires immediate updating. to change block locking during an erase operation: 1. write the erase suspend command. 2. check sr[6] to determine that the erase operation has suspended. 3. write the desired lock command sequence to a block. the lock status changes. 4. after completing lock, unlock, read, or program operations, resume the erase operation with the erase resume command (d0h). if a block is locked or locked-down during a suspended erase of the same block, the locking status bits change immediately. when the erase operation resumes, it completes normally. table 25: write protection truth table vpp wp# rst# write protection xxv il device is inaccessible v il xv ih word program and block erase are prohibited xv il v ih all lock-down blocks are locked xv ih v ih all lock-down blocks can be unlocked
numonyx? wireless flash memory (w30) datasheet november 2007 74 order number: 290702-13 numonyx? wireless flash memory (w30) locking operations cannot occur during program suspend. appendix a, ?write state machine? on page 86 shows valid commands during erase suspend. 13.1.6 status register error checking using nested locking or program command sequences during erase suspend can introduce ambiguity into status register results. because locking changes require 2-cycle command sequences?for example, 60h followed by 01h to lock a block?following the configuration setup command (60h) with an invalid command produces a command sequence error (sr[5:4]=11b). if a lock block command error occurs during erase suspend, the flash device sets sr[4] and sr[5] to 1 even after the erase resumes. when erase is complete, possible errors during the erase cannot be detected from the status register, because of the previous locking command error. a similar situation occurs if a program operation error is nested within an erase suspend. 13.1.7 wp# lock-down control the write protect signal, wp#, adds an additional layer of block security. wp# affects only blocks that previously had the lock-down command written to them. ? after the lock-down status bit is set for a block, asserting wp# forces that block into the lock-down state [011] and prevents it from being unlocked. ? after wp# is deasserted, the state of the block reverts to locked [111]. software commands can then unlock the block (for erase or program operations) and subsequently re-lock it. only flash device reset or power-down can clear the lock-down status bit and render wp# ineffective.
november 2007 datasheet order number: 290702-13 75 numonyx? wireless flash memory (w30) 13.2 protection register the w30 flash memory device includes a 128-bit protection register. this protection register is used to increase system security and for identification purposes. the protection register value can match the flash device to the system cpu or asic to prevent flash device substitution. ? the lower 64 bits within the protection register are programmed by numonyx with a unique number in each flash device. ? the upper 64 otp bits within the protection register are left for the customer to program. once programmed, the customer segment can be locked to prevent further programming. note: the individual bits of the user segment of the protection register are otp, not the register in total. the user can program each otp bit individually, one at a time, if desired. however, after the protection register is locked, the entire user segment is locked and no more user bits can be programmed. the protection register shares some of the same internal flash device resources as the parameter partition. therefore, rww is allowed only between the protection register and the main partitions. ta b l e 2 6 describes the operations allowed in the protection register, parameter partition, and main partition during rww and rwe. figure 34: locking operations flowchart no optional start write 60h block address write 90h bba + 02h read block lock status locking change? lock change complete write 01,d0,2fh block address write ffh partition address yes write write write (optional) read (optional) standby (optional) write lock setup lock, unlock, or lockdown confirm read id plane block lock status read array data = 60h addr = block to lock/unlock/lock-down (ba) data = 01h (lock block) d0h (unlock block) 2fh (lockdown block) addr = block to lock/unlock/lock-down (ba) data = 90h addr = bba + 02h block lock status data addr = bba + 02h confirm locking change on dq[1:0]. (see block locking state transitions table for valid combinations.) data = ffh addr = any address in same partition bus operation command comments locking operations procedure
numonyx? wireless flash memory (w30) datasheet november 2007 76 order number: 290702-13 numonyx? wireless flash memory (w30) 13.2.1 reading the protection register writing the read identifier command allows the protection register data to be read 16 bits at a time from addresses shown in table 20, ?flash device identification codes? on page 55 . the protection register is read from the read identifier command, and can be read in any partition.writing the read array command returns the flash device to read- array mode. 13.2.2 programing the protection register issue the protection program command only at the parameter partition followed by the data to be programmed at the specified location. this command programs the upper 64 bits of the protection register 16 bits at a time. table 20, ?flash device identification codes? on page 55 shows allowable addresses. see also figure 35, ?protection register programming flowchart? on page 77 . issuing a protection program command outside the address space of the register results in a status register error (sr[4]=1). 13.2.3 locking the protection register ? pr-lk.0 is programmed to 0 by numonyx to protect the unique flash device number. ? pr-lk.1 can be programmed by the user to lock the user portion (upper 64 bits) of the protection register (see figure 36, ?protection register locking ). this bit is set using the protection program command to program a value of fffdh into pr-lk. after pr-lk register bits are programmed (locked), the stored values in the protection register cannot be changed. protection program commands written to a locked section result in a status register error (sr[4]=1, sr[5]=1). table 26: simultaneous operations allowed with the protection register protection register parameter partition array data main partitions description read see description write/erase while programming or erasing in a main partition, the protection register can be read from any other partition. reading the parameter partition data is not allowed if the protection register is being read from addresses within the parameter partition. see description read write/erase while programming or erasing in a main partition, read operations are allowed in the parameter partition. accessing the protection registers from parameter partition addresses is not allowed. read read write/erase while programming or erasing in a main partition, read operations are allowed in the parameter partition. accessing the protection registers is allowed, but only in a partition that is different from the partition being programmed or erased, and also different from the parameter partition. write no access allowed read while programming the protection register, reads are allowed only in the other main partitions. access to the parameter partition is not allowed, because programming of the protection register can occur only in the parameter partition, so that the parameter partition exists in status mode. no access allowed write/erase read while programming or erasing the parameter partition, reads of the protection registers are not allowed in any partition. reads in other main partitions are supported.
november 2007 datasheet order number: 290702-13 77 numonyx? wireless flash memory (w30) . figure 35: protection register programming flowchart full status check procedure protection program operations addresses must be within the protection register address space. addresses outside this space will return an error. repeat for subsequent programming operations. full status register check can be done after each program or after a sequence of program operations. sr[3] must be cleared before the wsm will allow further program attempts. only the clear staus register command clears sr[4:3,1]. if an error is detected, clear the status register before attempting a program retry or other error recovery. yes no 1,1 1,0 1,1 protection register programming procedure start write c0h addr=prot addr write protect. register address / data read status register sr[7] = 1? full status check (if desired) program complete read srd program successful sr[4:3] = sr[4,1] = sr[4,1] = v pp range error programming error locked-register program aborted standby standby bus operation command sr[1] sr[3] sr[4] 011v pp error 0 0 1 protection register program error comments write write standby protection program setup protection program data = c0h addr = protection address data = data to program addr = protection address check sr[7] 1 = wsm ready 0 = wsm busy bus operation command comments read read srd toggle ce# or oe# to update srd standby 1 0 1 register locked; operation aborted
numonyx? wireless flash memory (w30) datasheet november 2007 78 order number: 290702-13 numonyx? wireless flash memory (w30) 13.3 vpp protection the product name provides in-system program and erase at v ppl . for factory programming, the w30 flash memory device also includes a low-cost, backward- compatible 12 v programming feature.( see ?factory programming? on page 60. ) the efp feature can also be used to greatly improve factory program performance, as explained in section 11.3, ?enhanced factory program (efp)? on page 61 . in addition to flexible block locking, holding the v pp programming voltage low can provide hardware write protection of all flash-device blocks. if v pp is below v pplk , program or erase operations result in an error displayed in sr[3]. (see figure 37 .) note: if the v cc supply can sink adequate current, you can use an appropriately valued resistor. figure 36: protection register locking 0x84 0x88 0x85 0x81 0x80 pr lock register 0 user-programmable intel factory-programmed 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 figure 37: examples of vpp power supply configurations ? 12 v fast programming ? absolute write protection with v pp v pplk system supply (note 1) vcc vpp 12 v supply ? low voltage and 12 v fast programming system supply 12 v supply ? low-voltage programming ? absolute write protection via logic signal system supply prot# (logic signal) ? low-voltage programming system supply 10k vcc vpp vcc vpp vcc vpp
november 2007 datasheet order number: 290702-13 79 numonyx? wireless flash memory (w30) 14.0 set read configuration register the set read configuration register (rcr) command sets the burst order, frequency configuration, burst length, and other parameters. a two-bus cycle command sequence initiates this operation. the read configuration register data is placed on the lower 16 bits of the address bus (a[15:0]) during both bus cycles. 1. the set read configuration register command is written, along with the configuration data (on the address bus). 2. a second write confirms the operation and again presents the read configuration register data on the address bus. 3. the read configuration register data is latched on the rising edge of adv#, ce#, or we# (whichever occurs first). this command functions independently of the applied v pp voltage. after executing this command, the flash device returns to read-array mode. to examine the contents of the read configuration register, write the read identifier command and then read location 05h. (see tab le 27 and ta b l e 2 8 .) table 27: read configuration register definitions read mod e res?d first access latency count wait polarit y data outpu t config wai t confi g burs t seq cloc k confi g res? d res? d burs t wra p burst length rm r lc2 lc1 lc0 wp doc wc bs cc r r bw bl2 bl1 bl0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 table 28: read configuration register descriptions (sheet 1 of 2) bit name description 1 notes 15 rm read mode 0 = synchronous burst reads enabled 1 = asynchronous reads enabled (default) 2 ,6 14 r reserved 5 13-11 lc[2:0] first access latency count 001 = reserved 010 = code 2 011 = code 3 100 = code 4 101 = code 5 111 = reserved (default) 6 10 wp wait signal polarity 0 = wait signal is asserted low 1 = wait signal is asserted high (default) 3 9 doc data output configuration 0 = hold data for one clock 1 = hold data for two clock (default) 6 8 wc wait configuration 0 = wait asserted during delay 1 = wait asserted one data cycle before delay (default) 6 7 bs burst sequence 1 = linear burst order (default) 6 cc clock configuration 0 = burst starts and data output on falling clock edge 1 = burst starts and data output on rising clock edge (default) 5rreserved 5 4rreserved 5
numonyx? wireless flash memory (w30) datasheet november 2007 80 order number: 290702-13 numonyx? wireless flash memory (w30) 14.1 read mode (rcr[15]) all partitions support two high-performance read configurations and rcr[15] sets the read configuration to one of these modes: ? synchronous burst mode ? asynchronous page mode (default) status register, query, and identifier modes support only asynchronous and single- synchronous read operations. 14.2 first access latency count (rcr[13:11]) the first access latency count (rcr[13:11]) configuration tells the flash device how many clocks must elapse from adv# de-assertion (v ih ) before driving the first data word onto its data pins. the input clock frequency determines this value. see table 27, ?read configuration register definitions? on page 79 for latency values. figure 38 shows data output latency from adv# assertion for different latencies. refer to section 14.2.1, ?latency count settings? on page 81 for latency code settings. note: other first access latency configuration settings are reserved. ) 3 bw burst wrap 0 = wrap bursts within burst length set by cr[2:0] 1 = don?t wrap accesses within burst length set by cr[2:0].(default) 2-0 bl[2:0] burst length 001 = 4-word burst 010 = 8-word burst 011 = 16-word burst (available on the 130 nm lithography) 111 = continuous burst (default) 4 notes: 1. undocumented combinations of bits are reserved by numonyx for future implementations. 2. synchronous and page read mode configurations affect reads from main blocks and parameter blocks. status register and configuration reads support single read cycles. rcr[15]=1 disables the configuration set by rcr[14:0]. 3. data is not ready when wait is asserted. 4. set the synchronous burst length. in asynchronous page mode, the burst length equals four words. 5. set all reserved read configuration register bits to zero. 6. setting the read configuration register for synchronous burst-mode with a latency count of 2 (rcr[13:11] = 010), data hold for 2 clocks (rcr[9] = 1), and wait asserted one data cycle before delay (rcr[8] =1) is not supported. table 28: read configuration register descriptions (sheet 2 of 2) bit name description 1 notes figure 38: first access latency configuration code 5 code 4 code 3 code 2 valid address valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output address [a] adv# [v] clk [c] d[15:0] [q] d[15:0] [q] d[15:0] [q] d[15:0] [q]
november 2007 datasheet order number: 290702-13 81 numonyx? wireless flash memory (w30) note: the 16-word boundary is the end of the flash device sense word-line. 14.2.1 latency count settings 14.3 wait signal polarity (rcr[10]) ? if the wt bit is cleared (rcr[10]=0), then wait is configured to be asserted low. a 0 on the wait signal indicates that data is not ready and the data bus contains invalid data. ? conversely, if rcr[10] is set, then wait is asserted high. figure 39: word boundary table 29: latency count settings t avqv /t chqv (85ns/22ns) t avqv /t chqv (70ns/20ns) t avqv /t chqv (90ns/22ns) unit latency count settings 2 3, 4, 5 2, 3, 4, 5 2 3, 4, 5 frequency < 31 < 33 < 40 < 29 < 33 mhz figure 40: data output with lc setting at code 3 0123456789abcdef 16 word boundary word 0 - 3 word 4 - 7 word 8 - b word c - f 4 word boundary a max-0 (a) dq 15-0 (d/q) clk (c) ce# (e) adv# (v) r103 valid output valid output high z t add-delay t data 1nd 0st 2rd 3th 4th valid address code 3
numonyx? wireless flash memory (w30) datasheet november 2007 82 order number: 290702-13 numonyx? wireless flash memory (w30) in either case, if wait is deasserted, then data is ready and valid. wait is asserted during asynchronous page mode reads. 14.4 wait signal function the wait signal indicates data valid when the flash device is operating in synchronous mode (rcr[15]=0), and when addressing a partition that is currently in read-array mode. the wait signal is deasserted only when data is valid on the bus. ? when the flash device is operating in synchronous non-read-array mode, such as read status, read id, or read query, wait is set to an asserted state, as determined by rcr[10]. see figure 14, ?wait signal in synchronous non-read array operation waveform? on page 37 . ? when the flash device is operating in asynchronous page mode or asynchronous single word read mode, wait is set to an asserted state, as determined by rcr[10]. see figure 10, ?page-mode read operation waveform? on page 33 , and figure 8, ?asynchronous read operation waveform? on page 31 . from a system perspective, the wait signal is in the asserted state (based on rcr[10]) when the flash device is operating in synchronous non-read-array mode (such as read id, read query, or read status), or if the flash device is operating in asynchronous mode (rcr[15]=1). in these cases, the system software must ignore (mask) the wait signal, because wait does not convey any useful information about the validity of what is appearing on the data bus. 14.5 data hold (rcr[9]) the data output configuration (doc) bit (rcr[9]) determines whether a data word remains valid on the data bus for one or two clock cycles. the minimum data set-up time on the processor, and the flash memory clock-to-data output delay, determine whether one or two clocks are needed. ? a doc set at 1-clock data hold co rresponds to a 1-clock data cycle. ? a doc set at 2-clock data hold co rresponds to a 2-clock data cycle. the setting of this configuration bit depends on the system and cpu characteristics. for clarification, see figure 41 . the following is a method for determining this configuration setting. to set the flash device at 1-clock data hold for subsequent reads, the following condition must be satisfied: t chqv (ns) + t data (ns) < one clk period (ns) as an example, use a clock frequency of 54 mhz and a clock period of 25 ns. assume the data output hold time is one clock. apply this data to the formula above for the subsequent reads: condition wait ce# = v ih ce# = v il tr i - s t a t e active oe# no-effect synchronous array read active synchronous non-array read asserted all asynchronous read and all write asserted
20 ns + 4 ns 25 ns this equation is satisfied, and data output is available and valid at every clock period. if t data is long, hold for two cycles. during page-mode reads, the initial access time can be determined using the formula: t add-delay (ns) t data (ns) + t avqv (ns) subsequent reads in page mode are defined by: t apa (ns) + t data (ns) (minimum time) note: wait shown asserted high (rcr[10]=1). 14.6 wait delay (rcr[8]) the wait configuration bit (rcr[8]) controls wait signal delay behavior for all synchronous read-array modes. this bit setting depends on the system and cpu characteristics. the wait can be asserted either during , or one data cycle before , a valid output. in synchronous linear read array (no-wrap mode rcr[3]=1) of 4-word, 8-word, 16- word, or continuous-word burst mode, an output delay might occur when a burst sequence crosses its first flash device-row boundary (16-word boundary). ? if the burst start address is 4-word boundary aligned, the delay does not occur. ? if the start address is misaligned to a 4-word boundary, the delay occurs once per burst-mode read sequence. the wait signal informs the system of this delay. 14.7 burst sequence (rcr[7]) the burst sequence specifies the synchronous-burst mode data order (see ta b l e 3 0 , ?sequence and burst length? on page 84 ). when operating in a linear burst mode, either 4-word, 8-word, or 16-word burst length with the burst wrap bit (rcr[3]) set, or in continuous burst mode, the flash device might incur an output delay when the burst sequence crosses the first 16-word boundary. (see figure 39, ?word boundary? on page 81 for word boundary description.) figure 41: data output configuration with wait signal delay dq 15-0 [q] clk [c] valid output valid output valid output dq 15-0 [q] valid output 1 clk data hold wait (cr.8 = 1) wait (cr.8 = 0) t chqv t chqv wait (cr.8 = 0) wait (cr.8 = 1) 2 clk data hold t chtl/h note 1 note 1 note 1 note 1 valid output
numonyx? wireless flash memory (w30) datasheet november 2007 84 order number: 290702-13 numonyx? wireless flash memory (w30) whether this delay occurs depends on the starting address. ? if the starting address is aligned to a 4-word boundary, there is no delay. ? if the starting address is the end of a 4-word boundary, the output delay is one clock cycle less than the first access latency count; this is the worst-case delay. the delay takes place only once, and only if the burst sequence crosses a 16-word boundary. the wait pin informs the system of this delay. for timing diagrams of wait functionality, see these figures: ? figure 11, ?single synchronous read-array operation waveform? on page 34 ? figure 12, ?synchronous 4-word burst read operation waveform? on page 35 ? figure 13, ?wait functionality for eowl (end-of-word line) condition waveform? on page 36 note: available on the 130 nm lithography. table 30: sequence and burst length start addr. (dec) burst addressing sequence (decimal) 4-word burst cr[2:0]=001b 8-word burst cr[2:0]=010b 16-word burst1 cr[2:0]=011b continuous burst cr[2:0]=111b linear linear linear linear wrap (cr[3]=0) 0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2...14-15 0-1-2-3-4-5-6-... 1 1-2-3-0 1-2-3-4-5-6-7-0 1-2-3...14-15-0 1-2-3-4-5-6-7-... 2 2-3-0-1 2-3-4-5-6-7-0-1 2-3-4...15-0-1 2-3-4-5-6-7-8-... 3 3-0-1-2 3-4-5-6-7-0-1-2 3-4-5...15-0-1-2 3-4-5-6-7-8-9-... 4 4-5-6-7-0-1-2-3 4-5-6...15-0-1-2-3 4-5-6-7-8-9-10... 5 5-6-7-0-1-2-3-4 5-6-7...15-0-1...4 5-6-7-8-9-10-11... 6 6-7-0-1-2-3-4-5 6-7-8...15-0-1...5 6-7-8-9-10-11-12-... 7 7-0-1-2-3-4-5-6 7-8-9...15-0-1...6 7-8-9-10-11-12-13... ... ... ... ... ... 14 14-15-0-1...13 14-15-16-17-18-19-20-... 15 15-0-1-2-3...14 15-16-17-18-19-... no-wrap (cr[3]=1) 0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2...14-15 0-1-2-3-4-5-6-... 1 1-2-3-4 1-2-3-4-5-6-7-8 1-2-3...15-16 1-2-3-4-5-6-7-... 2 2-3-4-5 2-3-4-5-6-7-8-9 2-3-4...16-17 2-3-4-5-6-7-8-... 3 3-4-5-6 3-4-5-6-7-8-9-10 3-4-5...17-18 3-4-5-6-7-8-9-... 4 4-5-6-7-8-9-10-11 4-5-6...18-19 4-5-6-7-8-9-10... 5 5-6-7-8-9-10-11-12 5-6-7...19-20 5-6-7-8-9-10-11... 6 6-7-8-9-10-11-12-13 6-7-8...20-21 6-7-8-9-10-11-12-... 7 7-8-9-10-11-12-13-14 7-8-9...21-22 7-8-9-10-11-12-13... ... ... ... ... ... 14 14-15...28-29 14-15-16-17-18-19-20-... 15 15-16...29-30 15-16-17-18-19-20-21-...
november 2007 datasheet order number: 290702-13 85 numonyx? wireless flash memory (w30) 14.8 clock edge (rcr[6]) configuring the valid clock edge enables a flexible memory interface to a wide range of burst cpus. clock configuration sets the flash device to start a burst cycle, output data, and assert wait on the rising or falling edge of the clock. 14.9 burst wrap (rcr[3]) the burst wrap bit determines whether 4-word, 8-word, or 16-word burst accesses wrap within the burst-length boundary, or they cross word-length boundaries to perform linear accesses. no-wrap mode (rcr[3]=1) enables wait to hold off the system processor, as it does in the continuous burst mode, until valid data is available. in no-wrap mode (rcr[3]=0), the flash device operates similarly to continuous linear burst mode, but consumes less power during 4-word, 8-word, or 16-word bursts. for example, if rcr[3]=0 (wrap mode) and rcr[2:0] = 1h (4-word burst), possible linear burst sequences are 0-1-2-3, 1-2-3-0, 2-3-0-1, 3-0-1-2. if rcr[3]=1 (no-wrap mode) and rcr[2:0] = 1h (4-word burst length), then possible linear burst sequences are 0-1-2-3, 1-2-3-4, 2-3-4-5, and 3-4-5-6. rcr[3]=1 not only enables limited non-aligned sequential bursts, but also reduces power by minimizing the number of internal read operations. setting rcr[2:0] bits for continuous linear burst mode (7h) also achieves the above 4- word burst sequences. however, significantly more power might be consumed. the 1- 2-3-4 sequence, for example, consumes power during the initial access, again during the internal pipeline lookup as the processor reads word 2, and possibly again, depending on system timing, near the end of the sequence as the flash device pipelines the next 4-word sequence. rcr[3]=1 while in 4-word burst mode (no-wrap mode) reduces this excess power consumption. 14.10 burst length (rcr[2:0]) the burst length is the number of words the flash device outputs in a synchronous read access. 4-word, 8-word, 16-word, and continuous-word are supported. in 4-word, 8-word, or 16-word burst configuration, the burst wrap bit (rcr[3]) determines whether burst accesses wrap within word-length boundaries, or they cross word-length boundaries to perform a linear access. after an address is specified, the flash device outputs data until it reaches the end of its burstable address space. continuous burst accesses are linear only (burst wrap bit rcr[3] is ignored during continuous burst) and do not wrap within word-length boundaries (see table 30, ?sequence and burst length? on page 84 ).
numonyx? wireless flash memory (w30) datasheet november 2007 86 order number: 290702-13 numonyx? wireless flash memory (w30) appendix a write state machine ta b l e 3 1 shows the command state transitions, based on incoming commands. only one partition can be actively programming or erasing at a time. table 31: next state table (sheet 1 of 2) chi p next state after com m and in p ut read array (3 ) program setup (4,5) erase setup (4 ,5 ) enhanced factory pgm setup (4 ) be confirm, p/e resume, ulb confirm (9 ) program/ erase suspend read status clear status register (6) read id /q u e ry (ffh ) (10h /40h ) (20h ) (30h) (d 0h ) (b0h ) (70h) (50h ) (90h , 98h) ready r eady program setup erase setup efp setup ready lock/c r s etup r eady (lock error) ready r eady (lock e rror) setup otp busy busy setup program busy busy program busy pgm susp program busy suspend program suspend pgm busy program suspend s etup r eady (error) erase busy r eady (error) busy erase busy erase susp erase busy suspend erase suspend pgm in erase susp setup erase suspend erase busy erase suspend setup program in erase suspend busy busy program in erase suspend busy pgm susp in erase susp program in erase suspend busy s uspend program s uspend in erase suspend pgm in erase s usp busy program suspend in erase suspend erase suspend (lock error) erase susp erase suspend (l o c k e rro r) s etup r eady (error) efp b usy r eady (error) efp busy efp bus y (7 ) efp verify verif y bus y (7 ) out p ut next state after com m and in p ut status status status id /q u e ry w rite state m achine (w sm ) next state table o utput next state table (1) lock/c r s etup, lock/c r s etup in erase susp otp busy current chip state (8) ready, pgm busy, pgm suspend, erase busy, erase suspend, pgm in e rase s usp busy, p g m s u s p in e ra s e s u s p pgm setup, erase s etup, otp setup, pgm in erase susp setup, efp setup, efp busy, v e rify b u s y lock/c r s etup in erase suspend erase program program in erase s uspend otp enhanced factory program output does not change array (3 ) status output does not change status
november 2007 datasheet order number: 290702-13 87 numonyx? wireless flash memory (w30) notes: 1. the output state shows the type of data that appears at the outputs if the partition address is the same as the command address. ? a partition can be placed in read array, read status or read id/cfi, depending on the command issued. ? each partition stays in its last output state (array, id/cfi or status) until a new command changes it. the next wsm state does not depend on the output state of the partition. ? for example, if the partition #1 output state is read array and the partition #4 output state is read status, every read from partition #4 (without issuing a new command) outputs the status register. 2. illegal commands are any commands not defined in the command set. table 31: next state table (sheet 2 of 2) chi p next state after com m and in p ut lock, unlock, lock-dow n, cr setup (5) otp setup (5 ) lock block confirm (9) lock- down block confirm (9 ) write cr confirm (9 ) enhanced fact pgm e x it (b lk a d d < > w a 0 ) illegal com m ands or efp data (2 ) (60h) (c 0h) (01h ) (2fh ) (03h ) (x xxx h) (other codes) ready lock/cr setup otp setup ready lock/cr setup ready (lock error) ready ready ready ready (lock error) setup otp busy busy ready setup program busy n/a busy program busy ready suspend program suspend setup r ea dy (e rro r) busy erase busy erase busy ready suspend lock/cr setup in erase susp erase suspend s etup p rogram in e rase s uspend b usy busy program in erase suspend busy erase suspend suspend program suspend in erase suspend erase suspend (lock error) erase susp erase susp erase susp erase suspend (lock error) setup r ea dy (e rro r) efp busy efp bus y (7 ) efp verify efp bus y (7 ) efp verify verif y bus y (7 ) ready efp verif y (7) ready out p ut next state after com m and in p ut status status array status w rite state m achine (w sm ) n ext state table o utput next state table (1) program erase program in erase suspend current chip state (8) otp lock/c r s etup in erase suspend enhanced factory program o utput does not change o utput does not change wsm o peration completes n/a n/a n/a n/a o utput does not change a rray status pgm setup, erase setup, otp setup, pgm in erase susp setup, efp setup, efp busy, v e rify b u s y lock/c r s etup, lock/c r s etup in erase susp otp busy ready, pgm busy, pgm suspend, erase busy, erase suspend, pgm in erase susp busy, p g m s u s p in e ra s e s u s p
numonyx? wireless flash memory (w30) datasheet november 2007 88 order number: 290702-13 numonyx? wireless flash memory (w30) 3. all partitions default to read array mode at power-up. a read array command issued to a busy partition results in undetermined data when a partition address is read. 4. both cycles of two-cycle commands must be issued to the same partition address. if the two cycles are issued to different partitions, the address used for the second write cycle determines the active partition. both partitions output status information when read. 5. if the wsm is active, both cycles of a two-cycle command are ignored. this feature differs from previous numonyx flash memory devices. 6. the clear status command clears status register error bits, except when the wsm is running (pgm busy, erase busy, pgm busy in erase suspend, otp busy, efp modes) or suspended (erase suspend, pgm suspend, pgm suspend in erase suspend). 7. efp writes are allowed only when status register bit sr.0 = 0. efp is busy if the block address = the address at the efp confirm command. any other commands are treated as data. 8. the current state is the state of the wsm, not the state of the partition. 9. confirm commands (lock block, unlock block, lock-down block, configuration register) perform the operation and then move to the ready state. 10. in erase suspend mode, the only valid two-cycle commands are program word, lock/unlock/lockdown block, and cr write. both cycles of other two-cycle commands (program otp & confirm, efp setup & confirm, erase setup & confirm) are ignored. in program suspend or program suspend in erase suspend, both cycles of all two-cycle commands are ignored.
november 2007 datasheet order number: 290702-13 89 numonyx? wireless flash memory (w30) appendix b common flash interface this appendix defines the data structure or database returned by the common flash interface (cfi) query command. system software parses this structure to gain critical information, such as block size, density, x8/x16, and electrical specifications. once this information has been obtained, the software can determine which command sets to use to enable flash device writes, enable block erases, and otherwise control the flash device. the query is part of an overall specification for multiple command set and control interface descriptions, which is called the common flash interface, or cfi. b.1 query structure output the query database allows system software to obtain information for controlling the flash device. this section describes the flash device cfi-compliant interface that allows access to query data. query data are presented on the lowest-order data outputs (dq0-7) only. the numerical offset value is the address relative to the maximum bus width that the flash device supports. on the w30 family of flash memory devices, the query table device starting address is a 10h, which is a word address for x16 flash devices. for a word-wide (x16) flash device, the first two query-structure bytes, ascii q and r, appear on the low byte at word addresses 10h and 11h. ? this cfi-compliant flash device outputs 00h data on upper bytes. ? the flash device outputs ascii q in the low byte (dq 0-7 ) and 00h in the high byte (dq 8-15 ). at query addresses containing two or more bytes of information, the least significant data byte is presented at the lower address, and the most significant data byte is presented at the higher address. in all of the following tables, addresses and data are represented in hexadecimal notation, so the h suffix has been dropped. in addition, because the upper byte of word-wide flash devices is always 00h , the leading 00 has been dropped from the table notation, and only the lower byte value is shown. any x16 flash device outputs can be assumed to have 00h on the upper byte in this mode. table 32: summary of query structure output as a function of the flash device and mode device hex offset hex code asci i value device addresses 00010: 00011: 00012: 51 52 59 q r y
numonyx? wireless flash memory (w30) datasheet november 2007 90 order number: 290702-13 numonyx? wireless flash memory (w30) b.2 query structure overview the query command causes the flash device to display the common flash interface (cfi) query structure or database . ta b l e 3 4 summarizes the structure sub-sections and address locations. table 34: query structure notes: 1. refer to the section b.1, ?query structure output? on page 89 and offset 28h, for the detailed definition of the offset address as a function of the flash device bus width and mode. 2. ba = block address beginning location (for example, 08000h is the block 1?beginning location when the block size is 32k- word). 3. offset 15 defines p, which points to the primary numonyx-specific extended query table. b.3 block status register the block status register indicates whether an erase operation completed successfully, a given block is locked, or a given block can be accessed for flash memory program/ erase operations. block erase status (bsr.1) allows system software to determine the success of the last block erase operation. use bsr.1 just after power-up to verify that the vcc supply was not accidentally removed during an erase operation. table 33: example of query structure output of x16- and x8 flash devices word addressing: byte addressing: offset hex code value offset hex code value a x ?a 0 d 15 ?d 0 a x ?a 0 d 7 ?d 0 00010h 0051 ?q? 00010h 51 q 00011h 0052 ?r? 00011h 52 r 00012h 0059 ?y? 00012h 59 y 00013h p id lo prvendor 00013h p id lo prvendor 00014h p id hi id # 00014h p id lo id # 00015h p lo prvendor 00015h p id hi id # 00016h phi tbladr 00016h ... ... 00017h a id lo altvendor 00017h 00018h a id hi id # 00018h ... ... ... ... offset sub-section name descri p tion (1) 00000h manufacturer code 00001h device code ( ba+2 ) h (2) block status re g ister block-specific information 00004-fh reserved reserved for vendor-specific information 00010h cfi query identification string command set id and vendor data offset 0001bh system interface information device timing & voltage information 00027h device geometry definition flash device layout p (3) primary intel-specific extended query table vendor-defined additional information specific to the primary vendor algorithm
november 2007 datasheet order number: 290702-13 91 numonyx? wireless flash memory (w30) table 35: block status register notes: 1. ba = block address beginning location (for example, 08000h is the block 1 beginning location when the block size is 32k- word). b.4 cfi query identification string the identification string verifies that the component supports the common flash interface specification. it also indicates the specification version and supported vendor- specified command set(s). . offset len g th description add. v alue (ba+2)h (1) 1 block lock status register ba+2 --00 or --01 ba+2 (bit 0): 0 or 1 ba+2 (bit 1): 0 or 1 bsr 2?7: reserved for future use ba+2 (bit 2?7): 0 bsr.0 block lock status 0 = unlocked 1 = locked bsr.1 block lock-down status 0 = not locked down 1 = locked down table 36: cfi identification offset length description add. hex code value 10h 3 query-unique ascii string ?qry? 10: 11: 12: --51 --52 --59 q r y 13h 2 primary vendor command set and control interface id code. 16-bit id code for vendor-specified algorithms 13: 14: --03 --00 15h 2 extended query table primary algorithm address 15: 16: --39 --00 17h 2 alternate vendor command set and control interface id code. 0000h means no second vendor-specified algorithm exists 17: 18: --00 --00 19h 2 secondary algorithm extended query table address. 0000h means none exists 19: 1a: --00 --00
numonyx? wireless flash memory (w30) datasheet november 2007 92 order number: 290702-13 numonyx? wireless flash memory (w30) table 37: system interface information offset length description add. hex code value 1bh 1 1b: --17 1.7v 1ch 1 1c: --19 1.9v 1dh 1 1d: --b4 11.4v 1eh 1 1e: --c6 12.6v 1fh 1 ?n? such that t yp ical sin g le word p ro g ram time-out = 2 n s 20h 1 ?n? such that t yp ical max. buffer write time-out = 2 n s 24h 1 ?n? such that maximum buffer write time-out = 2 n times t yp ical 24: --00 na 25h 1 ?n? such that maximum block erase time-out = 2 n times t yp ical 25: --03 8s 26h 1 ?n? such that maximum chi p erase time-out = 2 n times t yp ical 26: --00 na v cc logic supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts v cc logic supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts v pp [programming] supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts v pp [programming] supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts
november 2007 datasheet order number: 290702-13 93 numonyx? wireless flash memory (w30) b.5 flash device geometry definition table 38: flash device geometry definition offset length description code 27h 1 ?n? such that device size = 2 n in number of b y tes 27: see table below 76543210 28h 2 ????x64x32x16x828:--01x16 15 14 13 12 11 10 9 8 ????????29:--00 2ah 2 ?n? such that maximum number of b y tes in write buffer = 2 n 2a: --00 0 2b: --00 2ch 1 2c: 2dh 4 erase block region 1 information 2d: bits 0?15 = y, y+1 = number of identical-size erase blocks 2e: bits 16?31 = z, region erase block(s) size are z x 256 bytes 2f: 30: 31h 4 erase block region 2 information 31: bits 0?15 = y, y+1 = number of identical-size erase blocks 32: bits 16?31 = z, region erase block(s) size are z x 256 bytes 33: 34: 35h 4 reserved for future erase block region information 35: 36: 37: 38: see table below see table below see table below see table below number of erase block regions (x) within device: 1. x = 0 means no erase blocking; the device erases in bulk 2. x specifies the number of device regions with one or more contiguous same-size erase blocks. 3. s y mmetricall y blocked p artitions have one blockin g re g ion flash device interface code assignment: "n" such that n+1 specifies the bit field that represents the flash device width ca p abilities as described in the table: address 32 mbit ?b ?t ?b ?t ?b ?t 27: --16 --16 --17 --17 --18 --18 28: --01 --01 --01 --01 --01 --01 29: --00 --00 --00 --00 --00 --00 2a: --00 --00 --00 --00 --00 --00 2b: --00 --00 --00 --00 --00 --00 2c: --02 --02 --02 --02 --02 --02 2d: --07 --3e --07 --7e --07 --fe 2e: --00 --00 --00 --00 --00 --00 2f: --20 --00 --20 --00 --20 --00 30: --00 --01 --00 --01 --00 --01 31: --3e --07 --7e --07 --fe --07 32: --00 --00 --00 --00 --00 --00 33: --00 --20 --00 --20 --00 --20 34: --01 --00 --01 --00 --01 --00 35: --00 --00 --00 --00 --00 --00 36: --00 --00 --00 --00 --00 --00 37: --00 --00 --00 --00 --00 --00 38: --00 --00 --00 --00 --00 --00 64 mbit 128 mbit
numonyx? wireless flash memory (w30) datasheet november 2007 94 order number: 290702-13 numonyx? wireless flash memory (w30) b.6 numonyx-specific extended query table table 39: primary vendor-specific extended query offset (1) length descri p tion hex p = 39h (optional flash features and commands) a dd. code v alue (p+0)h 3 primary extended query table 39: --50 "p" (p+1)h unique ascii string ?pri? 3a: --52 "r" (p+2)h 3b: --49 "i" (p+3)h 1 major version number, ascii 3c: --31 "1" (p+4)h 1 minor version number, ascii 3d: --33 "3" (p+5)h 4 optional feature and command support (1=yes, 0=no) 3e: --e6 (p+6)h bits 10?31 are reserved; undefined bits are ?0.? if bit 31 is 3f: --03 (p+7)h ?1? then another 31 bit field of optional features follows at 40: --00 (p+8)h the end of the bit?30 field. 41: --00 bit 0 chip erase supported bit 0 = 0 no bit 1 suspend erase supported bit 1 = 1 yes bit 2 suspend program supported bit 2 = 1 yes bit 3 legacy lock/unlock supported bit 3 = 0 no bit 4 queued erase supported bit 4 = 0 no bit 5 instant individual block locking supported bit 5 = 1 yes bit 6 protection bits supported bit 6 = 1 yes bit 7 pagemode read supported bit 7 = 1 yes bit 8 synchronous read supported bit 8 = 1 yes bit 9 simultaneous operations supported bit 9 = 1 yes (p+9)h 1 42: --01 bit 0 program supported after erase suspend bit 0 = 1 yes (p+a)h 2 block status register mask 43: --03 (p+b)h bits 2?15 are reserved; undefined bits are ?0? 44: --00 bit 0 block lock-bit status register active bit 0 = 1 yes bit 1 block lock-down bit status active bit 1 = 1 yes (p+c)h 1 45: --18 1.8v (p+d)h 1 46: --c0 12.0v supported functions after suspend: read array, status, query other supported operations are: bits 1?7 reserved; undefined bits are ?0? v cc logic supply highest performance program/erase voltage bits 0?3 bcd value in 100 mv bits 4?7 bcd value in volts v pp optimum program/erase supply voltage bits 0?3 bcd value in 100 mv bits 4?7 hex value in volts
november 2007 datasheet order number: 290702-13 95 numonyx? wireless flash memory (w30) table 41: burst read information for non-multiplexed flash device table 42: partition and erase-block region information table 40: protection register information offset (1) p = 39h length description (optional flash device features and commands) add. hex code value (p+e)h 1 number of protection register fields in jedec id space. 00h indicates that 256 protection fields are available 47: --01 1 (p+f)h (p+10)h (p+11)h (p+12)h 4 protection field 1: protection description this field describes user-available one time programmable (otp) protection register bytes. ? some bytes are pre-programmed with flash device-unique serial numbers. ? other bytes are user programmable. bits 0-15 point to the protection register lock byte, the first byte in the section. the following bytes are factory pre-programmed and user- programmable. ? bits 0--7 = lock/bytes jedec-plane physical low address ? bits 8--15 = lock/bytes jedec-plane physical high address ? bits 16--23 = n such that 2 n = factory pre-programmed bytes ? bits 24--31 = n such that 2 n = user programmable bytes 48: 49: 4a: 4b: --80 --00 --03 --03 80h 00h 8 byte 8 byte offset (1) len g th description hex p = 39h (optional flash features and commands) a dd. code v alue (p+13)h 1 4c: --03 8 byte (p+14)h 1 4d: --04 4 (p+15)h 1 4e: --01 4 (p+16)h 1 synchronous mode read capability configuration 2 4f: --02 8 (p+17)h 1 synchronous mode read capability configuration 3 50: --03 16 (p+18)h 1 synchronous mode read capability configuration 4 51: --07 cont page mode read capability bits 0?7 = ?n? such that 2 n hex value represents the number of read-page bytes. see offset 28h for device word width to determine page-mode data output width. 00h indicates no read p a g e buffer. number of synchronous mode read configuration fields that follow. 00h indicates no burst capability. synchronous mode read capability configuration 1 bits 3?7 = reserved bits 0?2 ?n? such that 2 n+1 hex value represents the maximum number of continuous synchronous reads when the device is configured for its maximum word width. a value of 07h indicates that the device is capable of continuous linear bursts that will output data until the internal burst counter reaches the end of the device?s burstable address space. this field?s 3-bit value can be written directly to the read configuration register bits 0?2 if the device is configured for its maximum word width. see offset 28h for word width to determine the burst data out p ut width. offset (1) see table below p = 39h descri p tion a ddress bottom top ( optional flash features and commands ) len bot top (p+19)h (p+19)h 1 52: 52: number of device hardware-partition regions within the device. x = 0: a single hardware partition device (no fields follow). x specifies the number of device partition regions containing one or more contiguous erase block regions.
numonyx? wireless flash memory (w30) datasheet november 2007 96 order number: 290702-13 numonyx? wireless flash memory (w30) table 43: partition region 1 information offset (1) see table below p = 39h description a ddress bottom to p ( o p tional flash features and commands ) len bot top (p+1a)h (p+1a)h number of identical partitions within the partition region 2 53: 53: (p+1b)h (p+1b)h 54: 54: (p+1c)h (p+1c)h 1 55: 55: (p+1d)h (p+1d)h 1 56: 56: (p+1e)h (p+1e)h 1 57: 57: (p+1f)h (p+1f)h 1 58: 58: (p+20)h (p+20)h partition region 1 erase block type 1 information 4 59: 59: (p+21)h (p+21)h bits 0?15 = y, y+1 = number of identical-size erase blocks 5a: 5a: (p+22)h (p+22)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 5b: 5b: (p+23)h (p+23)h 5c: 5c: (p+24)h (p+24)h partition 1 (erase block type 1) 25d:5d: (p+25)h (p+25)h minimum block erase cycles x 1000 5e: 5e: (p+26)h (p+26)h 1 5f: 5f: (p+27)h (p+27)h 1 60: 60: (p+28)h partition region 1 erase block type 2 information 4 61: (p+29)h bits 0?15 = y, y+1 = number of identical-size erase blocks 62: (p+2a)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 63: (p+2b)h (bottom parameter device only) 64: (p+2c)h partition 1 ( erase block t y pe 2 ) 2 65: (p+2d)h minimum block erase cycles x 1000 66: (p+2e)h 1 67: (p+2f)h 1 68: simultaneous program or erase operations allowed in other partitions while a partition in this region is in program mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations simultaneous program or erase operations allowed in other partitions while a partition in this region is in erase mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations number of program or erase operations allowed in a partition bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations partition 1 (erase block type 1) bits per cell; internal ecc bits 0?3 = bits per cell in erase region bit 4 = reserved for ?internal ecc used? (1=yes, 0=no) bits 5?7 = reserve for future use partition 1 (erase block type 1) page mode and synchronous mode capabilities defined in table 10. bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host writes permitted (1=yes, 0=no) bits 3?7 = reserved for future use partition 1 (erase block type 2) bits per cell bits 0?3 = bits per cell in erase region bit 4 = reserved for ?internal ecc used? (1=yes, 0=no) bits 5?7 = reserve for future use partition 1 (erase block type 2) pagemode and synchronous mode capabilities defined in table 10 bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host writes permitted (1=yes, 0=no) bits 3?7 = reserved for future use types of erase block regions in this partition region. x = 0 = no erase blocking; the partition region erases in bulk x = number of erase block regions w/ contiguous same-size erase blocks. symmetrica lly blocked partitions have one blocking region. partition size = (type 1 blocks)x(type 1 block sizes) + (type 2 blocks)x(type 2 block sizes) +?+ ( t y pe n blocks ) x ( t y pe n block sizes )
november 2007 datasheet order number: 290702-13 97 numonyx? wireless flash memory (w30) table 44: partition region 2 information offset (1) see table below p = 39h descri p tion a ddress bottom top ( optional flash features and commands ) len bot top (p+30)h (p+28)h number of identical partitions within the partition region 2 69: 61: (p+31)h (p+29)h 6a: 62: (p+32)h (p+2a)h 1 6b: 63: (p+33)h (p+2b)h 1 6c: 64: (p+34)h (p+2c)h 1 6d: 65: (p+35)h (p+2d)h 1 6e: 66: (p+36)h (p+2e)h partition region 2 erase block type 1 information 4 6f: 67: (p+37)h (p+2f)h bits 0?15 = y, y+1 = number of identical-size erase blocks 70: 68: (p+38)h (p+30)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 71: 69: (p+39)h (p+31)h 72: 6a: (p+3a)h (p+32)h partition 2 (erase block type 1) 2 73: 6b: (p+3b)h (p+33)h minimum block erase cycles x 1000 74: 6c: (p+3c)h (p+34)h 1 75: 6d: (p+3d)h (p+35)h 1 76: 6e: (p+36)h partition region 2 erase block type 2 information 4 6f: (p+37)h bits 0?15 = y, y+1 = number of identical-size erase blocks 70: (p+38)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 71: (p+39)h 72: (p+3a)h partition 2 (erase block type 2) 273: (p+3b)h minimum block erase cycles x 1000 74: (p+3c)h 1 75: (p+3d)h 1 76: (p+3e)h (p+3e)h features space definitions (reserved for future use) tbd 77: 77: (p+3f)h (p+3f)h reserved for future use resv'd 78: 78: partition 2 (erase block type 2) bits per cell bits 0?3 = bits per cell in erase region bit 4 = reserved for ?internal ecc used? (1=yes, 0=no) bits 5?7 = reserved for future use partition 2 (erase block type 2) pagemode and synchronous mode capabilities as defined in table 10. bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host writes permitted (1=yes, 0=no) bits 3?7 = reserved for future use simultaneous program or erase operations allowed in other partitions while a partition in this region is in erase mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations types of erase block regions in this partition region. x = 0 = no erase blocking; the partition region erases in bulk x = number of erase block regions w/ contiguous same-size erase blocks. symmetrically blocked partitions have one blocking region. partition size = (type 1 blocks)x(type 1 block sizes) + (type 2 blocks)x(type 2 block sizes) +?+ (type n blocks)x(type n block sizes) partition 2 (erase block type 1) bits per cell bits 0?3 = bits per cell in erase region bit 4 = reserved for ?internal ecc used? (1=yes, 0=no) bits 5?7 = reserve for future use partition 2 (erase block type 1) pagemode and synchronous mode capabilities as defined in table 10. bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host writes permitted (1=yes, 0=no) bits 3?7 = reserved for future use simultaneous program or erase operations allowed in other partitions while a partition in this region is in program mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations number of program or erase operations allowed in a partition bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations
numonyx? wireless flash memory (w30) datasheet november 2007 98 order number: 290702-13 numonyx? wireless flash memory (w30) table 45: partition and erase-block region information notes: 1. the p variable is a pointer which is defined at cfi offset 15h. 2. tpd - top parameter device. bpd - bottom parameter device. 3. partition: each partition is 4 mb in size. it can contain main blocks or a combination of both main and parameter blocks. 4. partition region: symmetrical partitions form a partition region. ? partition region a. contains all partitions that are made up of main blocks only. ? partition region b. contains the partition that is made up of the parameter and the main blocks. address 32 mbit ? b ? t ? b ? t ? b ? t 52: --02 --02 --02 --02 --02 --02 53: --01 --07 --01 --0f --01 --1f 54: --00 --00 --00 --00 --00 --00 55: --11 --11 --11 --11 --11 --11 56: --00 --00 --00 --00 --00 --00 57: --00 --00 --00 --00 --00 --00 58: --02 --01 --02 --01 --02 --01 59: --07 --07 --07 --07 --07 --07 5a: --00 --00 --00 --00 --00 --00 5b: --20 --00 --20 --00 --20 --00 5c: --00 --01 --00 --01 --00 --01 5d: --64 --64 --64 --64 --64 --64 5e: --00 --00 --00 --00 --00 --00 5f: --01 --01 --01 --01 --01 --01 60: --03 --03 --03 --03 --03 --03 61: --06 --01 --06 --01 --06 --01 62: --00 --00 --00 --00 --00 --00 63: --00 --11 --00 --11 --00 --11 64: --01 --00 --01 --00 --01 --00 65: --64 --00 --64 --00 --64 --00 66: --00 --02 --00 --02 --00 --02 67: --01 --06 --01 --06 --01 --06 68: --03 --00 --03 --00 --03 --00 69: --07 --00 --0f --00 --1f --00 6a: --00 --01 --00 --01 --00 --01 6b: --11 --64 --11 --64 --11 --64 6c: --00 --00 --00 --00 --00 --00 6d: --00 --01 --00 --01 --00 --01 6e: --01 --03 --01 --03 --01 --03 6f: --07 --07 --07 --07 --07 --07 70: --00 --00 --00 --00 --00 --00 71: --00 --20 --00 --20 --00 --20 72: --01 --00 --01 --00 --01 --00 73: --64 --64 --64 --64 --64 --64 74: --00 --00 --00 --00 --00 --00 75: --01 --01 --01 --01 --01 --01 76: --03 --03 --03 --03 --03 --03 64mbit 128mbit
november 2007 datasheet order number: 290702-13 99 numonyx? wireless flash memory (w30) appendix c ordering information to order samples, obtain datasheets or inquire about any stack combination, please contact your local numonyx representative. table 46: 38f type stacked components pf 38f 5070 m0 y 0 b 0 package designator product line designator product die/ density configuration nor flash product family voltage/nor flash ce# configuration parameter / mux configuration ballout identifier device details pf = scsp, rohs rd = scsp, leaded stacked nor flash + ram char 1 = flash die #1 char 2 = flash die #2 char 3 = ram die #1 char 4 = ram die #2 (see table 48, ?38f / 48f density decoder? on page 100 for details) first character applies to flash die #1 second character applies to flash die #2 (see table 49, ?nor flash family decoder? on page 101 for details) v = 1.8 v core and i/o; separate chip enable per die (see table 50, ?voltage / nor flash ce# configurati on decoder? on page 101 for details) 0 = no parameter blocks; non- mux i/o interface (see ta b l e 5 1 , ?paramete r / mux configurati on decoder? on page 101 for details) b = x16d ballout (see tab le 5 2, ?ballout decoder ? on page 10 2 for details) 0 = original released version of this product
numonyx? wireless flash memory (w30) datasheet november 2007 100 order number: 290702-13 numonyx? wireless flash memory (w30) table 47: 48f type stacked components pc 48f 4400 p0 v b 0 0 package designator product line designator product die/ density configuration nor flash product family voltage/nor flash ce# configuration parameter / mux configuration ballout identifier device details pc = easy bga, rohs rc = easy bga, leaded js = tsop, rohs te = tsop, leaded pf = scsp, rohs rd = scsp, leaded stacked nor flash only char 1 = flash die #1 char 2 = flash die #2 char 3 = flash die #3 char 4 = flash die #4 (see ta b l e 4 8 , ?38f / 48f density decoder? on page 100 for details) first character applies to flash dies #1 and #2 second character applies to flash dies #3 and #4 (see table 49, ?nor flash family decoder? on page 101 for details) v = 1.8 v core and 3 v i/o; virtual chip enable (see table 50, ?voltage / nor flash ce# configurati on decoder? on page 101 for details) b = bottom parameter; non-mux i/o interface (see ta b l e 5 1 , ?paramete r / mux configurati on decoder? on page 101 for details) 0 = discrete ballout (see ta b l e 5 2, ?ballout decoder ? on page 10 2 for details) 0 = original released version of this product table 48: 38f / 48f density decoder code flash density ram density 0 no die no die 1 32-mbit 4-mbit 2 64-mbit 8-mbit 3 128-mbit 16-mbit 4 256-mbit 32-mbit 5 512-mbit 64-mbit 6 1-gbit 128-mbit 7 2-gbit 256-mbit 8 4-gbit 512-mbit 9 8-gbit 1-gbit a 16-gbit 2-gbit b 32-gbit 4-gbit c 64-gbit 8-gbit d 128-gbit 16-gbit e 256-gbit 32-gbit f 512-gbit 64-gbit
november 2007 datasheet order number: 290702-13 101 numonyx? wireless flash memory (w30) table 49: nor flash family decoder code family marketing name c c3 numonyx advanced+ boot block flash memory j j3v.d numonyx embedded flash memory l l18 / l30 numonyx strataflash? wireless memory m m18 numonyx strataflash? cellular memory p p30 / p33 numonyx stratafalsh? embedded memory w w18 / w30 numonyx wireless flash memory 0(zero) - no die table 50: voltage / nor flash ce# configuration decoder code i/o voltage (volt) core voltage (volt) ce# configuration z 3.0 1.8 seperate chip enable per die y 1.8 1.8 seperate chip enable per die x 3.0 3.0 seperate chip enable per die v 3.0 1.8 virtual chip enable u 1.8 1.8 virtual chip enable t 3.0 3.0 virtual chip enable r3.0 1.8 virtual address q1.8 1.8 virtual address p3.0 3.0 virtual address table 51: parameter / mux configuration decoder code, mux identificati on number of flash die bus width flash die 1 flash die 2 flash die 3 flash die 4 0 = non mux 1 = ad mux 1 2= aad mux 3 =full" ad mux 2 any na notation used for stacks that contain no parameter blocks b = non mux c = ad mux f = "full" ad mux 1 x16 bottom - - - 2 bottom top - - 3 bottom bottom top - 4 bottom top bottom top 2 x32 bottom bottom - - 4 bottom bottom top top
numonyx? wireless flash memory (w30) datasheet november 2007 102 order number: 290702-13 numonyx? wireless flash memory (w30) t = non mux u = ad mux w = "full" ad mux 1 x16 top - - - 2 top bottom - - 3 top top bottom - 4 top bottom top bottom 2 x32 top top - - 4 top top bottom bottom 1. only flash is muxed and ram is non-muxed 2. both flash and ram are ad-muxed table 52: ballout decoder code ballout definition 0 (zero) sdiscrete ballout (easay bga and tsop) b x16d ballout, 105 ball (x16 nor + nand + dram share bus) c x16c ballout, 107 ball (x16 nor + nand + psram share bus) q quad/+ ballout, 88 ball (x16 nor + psram share bus) u x32sh ballout, 106 ball (x32 nor only share bus) v x16sb ballout, 165 ball (x16 nor / nand + x16 dram split bus w x48d ballout, 165 ball (x16/x32 nor + nand + dram split bus table 51: parameter / mux configuration decoder code, mux identificati on number of flash die bus width flash die 1 flash die 2 flash die 3 flash die 4

▲Up To Search▲

Price & Availability of 28F128W30

	To Download 28F128W30 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .